[Apache Bloodhound] New user registration: JoKoT3
New user registration for user JoKoT3 -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] #787: [patch] mysql support in bloodhound_setup.py
#787: [patch] mysql support in bloodhound_setup.py -+ Reporter: JoKoT3 | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: installer|Version: 0.7.0 Keywords: mysql| -+ Hi, Here is a patch to bloodhound_setup.py to support an installation on mysql. It has been tested with the following installation type : - all needed parameters given - no parameters given, interactive installation - by providing the connectstring This is a follow-up to this conversation http://mail- archives.apache.org/mod_mbox/bloodhound-user/201403.mbox/browser -- Ticket URL: https://issues.apache.org/bloodhound/ticket/787 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #778: Ticket cannot be found if reporter is not an active user
#778: Ticket cannot be found if reporter is not an active user +--- Reporter: hb | Owner: hb Type: defect | Status: needinfo(new) Priority: major | Milestone: Component: dashboard |Version: 0.7.0 Resolution: | Keywords: +--- Comment (by rjollos): Replying to [comment:2 hb]: I have confirmed that renaming the reporter of an existing ticket to a non existing user does NOT make the ticket disappear from the list. (even after restarting apache) Sorry, but I'm not following the scenario. You are searching for a username, that is contained in the reporter field of a ticket, and you want to confirm that removing the user from the //Permissions table// does not effect whether the ticket appears in the search results? Certain ticket fields have the searchable property, so searching for a username should not depend on whether the user appears in the //Permissions// or //Session// table. The caching issues might lead to some misleading behavior when changing tickets though. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/778#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #787: [patch] mysql support in bloodhound_setup.py
#787: [patch] mysql support in bloodhound_setup.py --+-- Reporter: JoKoT3 | Owner: rjollos Type: enhancement | Status: accepted Priority: major| Milestone: next 0.x Component: installer|Version: 0.7.0 Resolution: | Keywords: mysql --+-- Changes (by rjollos): * owner: nobody = rjollos * status: new = accepted * milestone: = next 0.x Comment: Thanks for the patch. We might be able to get it into the upcoming release. If not, then Release 9. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/787#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] New user registration: guerilla
New user registration for user guerilla -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #237: Generic conversions still applied with different theme
#237: Generic conversions still applied with different theme +--- Reporter: olemis | Owner: olemis Type: defect | Status: assigned Priority: major | Milestone: next 0.x Component: dashboard |Version: Resolution: | Keywords: bootstrap +--- Changes (by olemis): * status: new = assigned * owner: nobody = olemis -- Ticket URL: https://issues.apache.org/bloodhound/ticket/237#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #338: Add boolean fields for widgets
#338: Add boolean fields for widgets --+-- Reporter: olemis | Owner: olemis Type: enhancement | Status: assigned Priority: minor| Milestone: Unscheduled Component: dashboard|Version: 0.3.0 Resolution: | Keywords: widget fields parameters --+-- Changes (by olemis): * owner: gjm = olemis * status: review = assigned -- Ticket URL: https://issues.apache.org/bloodhound/ticket/338#comment:16 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #338: Add boolean fields for widgets
#338: Add boolean fields for widgets --+-- Reporter: olemis | Owner: olemis Type: enhancement | Status: accepted Priority: minor| Milestone: Unscheduled Component: dashboard|Version: 0.3.0 Resolution: | Keywords: widget fields parameters --+-- Changes (by olemis): * status: assigned = accepted -- Ticket URL: https://issues.apache.org/bloodhound/ticket/338#comment:17 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
svn commit: r1574778 - /bloodhound/trunk/bloodhound_relations/bhrelations/validation.py
Author: rjollos Date: Thu Mar 6 06:03:15 2014 New Revision: 1574778 URL: http://svn.apache.org/r1574778 Log: 0.8dev: Moved `ValidationError` to the top of the module, per the convention in Trac. Modified: bloodhound/trunk/bloodhound_relations/bhrelations/validation.py Modified: bloodhound/trunk/bloodhound_relations/bhrelations/validation.py URL: http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_relations/bhrelations/validation.py?rev=1574778r1=1574777r2=1574778view=diff == --- bloodhound/trunk/bloodhound_relations/bhrelations/validation.py (original) +++ bloodhound/trunk/bloodhound_relations/bhrelations/validation.py Thu Mar 6 06:03:15 2014 @@ -26,6 +26,14 @@ from bhrelations.api import IRelationVal ResourceIdSerializer, TicketRelationsSpecifics +class ValidationError(TracError): +Exception raised when a validator fails. +def __init__(self, message, title=None, show_traceback=False): +super(ValidationError, self).__init__( +message, title, show_traceback) +self.failed_ids = [] + + class Validator(Component): implements(IRelationValidator) @@ -231,10 +239,3 @@ class BlockerValidator(Validator): error = ValidationError(error) error.failed_ids = path raise error - - -class ValidationError(TracError): -def __init__(self, message, title=None, show_traceback=False): -super(ValidationError, self).__init__( -message, title, show_traceback) -self.failed_ids = []
Re: [Apache Bloodhound] #775: Can't create multiple is a parent of relations
#775: Can't create multiple is a parent of relations
+
Reporter: rjollos| Owner: rjollos
Type: defect | Status: accepted
Priority: major | Milestone: Release 8
Component: relations |Version:
Resolution: | Keywords: validation
+
Description changed by rjollos:
Old description:
To reproduce:
* Create tickets A, B, C
* Create a relation: ticket A //is a parent of// B
* Create a relation: ticket A //is a parent of// C
The following error results:
{{{#!html
div class=alert alert-errorspan class=label label-importantOops
!/span
Could not create relation.
Resource emprod5:ticket:3/em can only have one bis a
parent of/b relation./div
}}}
It appears that the `OneToManyValidator` needs to be more specific with
regard to types of relations that it asserting on.
New description:
To reproduce:
* Create tickets A, B, C
* Create a relation: ticket A //is a parent of// B
* Create a relation: ticket A //is a parent of// C
The following error results:
{{{#!html
div class=alert alert-errorspan class=label label-importantOops
!/span
Could not create relation.
Resource emprod5:ticket:3/em can only have one bis a
parent of/b relation./div
}}}
It appears that the `OneToManyValidator` needs to be more specific with
regard to type of relation that it is asserting on.
Proposals/BEP-0006#Constraints describes the requirement for the
OneToManyValidator: //Parent/child relationships should be one-way (i.e.
tree hierarchy, not a graph with backward relationships).// I interpret
this even more simply as, //a ticket cannot have multiple parents.//
For reference, the `OneToManyValidator` was implemented in [1483676] for
#528.
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/775#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
