svn commit: r1513085 - /bloodhound/trunk/bloodhound_multiproduct/multiproduct/ticket/batch.py
Author: matevz Date: Mon Aug 12 08:53:46 2013 New Revision: 1513085 URL: http://svn.apache.org/r1513085 Log: Ref. #596 - fix for tickets in global scope Modified: bloodhound/trunk/bloodhound_multiproduct/multiproduct/ticket/batch.py Modified: bloodhound/trunk/bloodhound_multiproduct/multiproduct/ticket/batch.py URL: http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_multiproduct/multiproduct/ticket/batch.py?rev=1513085r1=1513084r2=1513085view=diff == --- bloodhound/trunk/bloodhound_multiproduct/multiproduct/ticket/batch.py (original) +++ bloodhound/trunk/bloodhound_multiproduct/multiproduct/ticket/batch.py Mon Aug 12 08:53:46 2013 @@ -40,7 +40,7 @@ class ProductBatchModifyModule(BatchModi global_env = ProductEnvironment.lookup_global_env(self.env) tmpenv = self.env for k,v in tickets_by_product.iteritems(): -self.env = ProductEnvironment(global_env, k) +self.env = ProductEnvironment(global_env, k) if k else global_env data['action_controls'] += self._get_action_controls(req, v) self.env = tmpenv batch_list_modes = [
Re: [Apache Bloodhound] #596: pagination on /dashboard confused
#596: pagination on /dashboard confused +-- Reporter: tim| Owner: olemis Type: defect | Status: assigned Priority: major | Milestone: Component: dashboard |Version: 0.6.0 Resolution: | Keywords: ticket query +-- Comment (by matevzb): Replying to [comment:13 olemis]: Replying to [comment:12 matevzb]: I couldn't reproduce above issues, but do you perhaps have any tickets in the database without associated products? Now I notice . I do recall the convention of using `product = ''` for global (environment) resources. If so, is this deliberate? Yes . Recall that I've never used default product in production, just for (automated) functional testing purposes . I've also performed (manual) tests for different features without having default products setup , because that's the way I always run BH . (As far as I understood the multiproduct implementation, each ticket should be associated to a product, otherwise we won't be able to perform global and scoped queries, searches etc. Or maybe we could, but with lots of problems.) I've not detected major problems until recently . I do not see why we should be breaking it either now and, considering the error messages, it seems to be just a matter of associating `product=''` with the global environment . I'll take a look and propose a patch for you to review . Please check if r1513085 solves the above issues. At least the first one should be resolved, I'm not sure about the latter (still can't reproduce the errors). -- Ticket URL: https://issues.apache.org/bloodhound/ticket/596#comment:14 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #630: No relations types after upgrading 0.5.3 instance
#630: No relations types after upgrading 0.5.3 instance +-- Reporter: olemis | Owner: matevzb Type: defect | Status: accepted Priority: major | Milestone: Component: relations |Version: 0.6.0 Resolution: | Keywords: upgrade +-- Comment (by astaric): It is enabled in new installations, as bloodhound_setup takes care of that. There is no obvious way to enable it on upgrade, as it is performed using trac-admin upgrade, which only upgrades already enabled modules. We could hack the environment upgrade participant of one of the existing component, but I do not think that is a good idea. If number of modules included by default will keep increasing, we might consider adding --upgrade switch to the bloodhound_setup and then using the script to upgrade from one version to another. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/630#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] #635: ProgrammingError: column product specified more than onceLINE 1: ...ne, component, version, keywords, cc, time, changetime, product) V... ^
#635: ProgrammingError: column product specified more than onceLINE 1:
...ne,component,version,keywords,cc,time,changetime, product) V...
^
--+
Reporter: jav | Owner: nobody
Type: defect| Status: new
Priority: blocker | Milestone:
Component: multiproduct |Version: 0.6.0
Keywords:|
--+
= Create Ticket results in DB error =
Creating a ticket results in a database error:
{{{
2013-08-12 14:13:30 CEST bloodhound bloodhound ERROR: column product
specified more than once at character 142
2013-08-12 14:13:30 CEST bloodhound bloodhound STATEMENT: INSERT INTO
ticket
(summary,reporter,owner,description,type,status,priority,product,milestone,component,version,keywords,cc,time,changetime,
product) VALUES
('test','admin','somebody','','defect','new','major','Root','','component1','','','',1376309610703945,1376309610703945,'@')
}}}
How to Reproduce
While doing a POST operation on `/newticket`, Trac issued an internal
error.
Click ''Create Ticket'' button - ''More Fields'' - enter ''Ticket
Summary'' - click ''Create Ticket'' button
Request parameters:
{{{
{'__FORM_TOKEN': u'6bc262035d3c5bd1685a62f1',
'comment': u'',
'field_cc': u'',
'field_component': u'component1',
'field_description': u'',
'field_keywords': u'',
'field_milestone': u'',
'field_priority': u'major',
'field_reporter': u'admin',
'field_summary': u'test',
'field_type': u'defect',
'field_version': u'',
'start_time': u'0',
'submit': u'Create ticket',
'view_time': u'0'}
}}}
User agent: `Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101
Firefox/23.0`
System Information
|| '''`Trac`''' || `1.0.1` [[br]] `` ||
|| '''`Babel`''' || `0.9.6` ||
|| '''`Bloodhound Trac`''' || `1.0.1` ||
|| '''`Genshi`''' || `0.7 (without speedups)` ||
|| '''`mod_wsgi`''' || `3.3 (WSGIProcessGroup bh_tracker
WSGIApplicationGroup %{GLOBAL})` ||
|| '''`psycopg2`''' || `2.4.5` ||
|| '''`Pygments`''' || `1.6` ||
|| '''`Python`''' || `2.7.3 (default, Apr 14 2012, 08:58:41) [GCC]` ||
|| '''`pytz`''' || `2013b` ||
|| '''`setuptools`''' || `0.9.8` ||
|| '''`jQuery`''' || `1.7.2` ||
Enabled Plugins
|| '''`BloodhoundDashboardPlugin`''' || `0.6.0` ||
|| '''`BloodhoundMultiProduct`''' || `0.6.0` ||
|| '''`BloodhoundRelationsPlugin`''' || `0.6.0` ||
|| '''`BloodhoundSearchPlugin`''' || `0.6.0` ||
|| '''`BloodhoundTheme`''' || `0.6.0` ||
|| '''`TracAccountManager`''' || `0.4.3` ||
|| '''`TracPermRedirect`''' || `3.0` ||
|| '''`TracThemeEngine`''' || `2.2.0` ||
Python Traceback
{{{
Traceback (most recent call last):
File /opt/apache-bloodhound-0.6/installer/bloodhound/lib/python2.7
/site-packages/trac/web/main.py, line 477, in _dispatch_request
dispatcher.dispatch(req)
File /opt/apache-bloodhound-0.6/installer/bloodhound/lib/python2.7
/site-packages/trac/web/main.py, line 214, in dispatch
resp = chosen_handler.process_request(req)
File /opt/apache-bloodhound-0.6/installer/bloodhound/lib/python2.7
/site-packages/multiproduct/ticket/web_ui.py, line 66, in process_request
return self._process_newticket_request(req)
File /opt/apache-bloodhound-0.6/installer/bloodhound/lib/python2.7
/site-packages/trac/ticket/web_ui.py, line 465, in
_process_newticket_request
self._do_create(req, ticket) # (redirected if successful)
File /opt/apache-bloodhound-0.6/installer/bloodhound/lib/python2.7
/site-packages/trac/ticket/web_ui.py, line 1289, in _do_create
ticket.insert()
File /opt/apache-bloodhound-0.6/installer/bloodhound/lib/python2.7
/site-packages/trac/ticket/model.py, line 241, in insert
[values[name] for name in std_fields])
File /opt/apache-bloodhound-0.6/installer/bloodhound/lib/python2.7
/site-packages/multiproduct/dbcursor.py, line 143, in execute
return self.cursor.execute(sql, args=args)
File /opt/apache-bloodhound-0.6/installer/bloodhound/lib/python2.7
/site-packages/multiproduct/dbcursor.py, line 83, in execute
return super(BloodhoundIterableCursor,
self).execute(translate_sql(self.env, sql), args=args)
File /opt/apache-bloodhound-0.6/installer/bloodhound/lib/python2.7
/site-packages/trac/db/util.py, line 65, in execute
return self.cursor.execute(sql_escape_percent(sql), args)
ProgrammingError: column product specified more than once
LINE 1: ...ne,component,version,keywords,cc,time,changetime, product) V...
^
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/635
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #635: ProgrammingError: column product specified more than onceLINE 1: ...ne, component, version, keywords, cc, time, changetime, product) V... ^
#635: ProgrammingError: column product specified more than onceLINE 1: ...ne,component,version,keywords,cc,time,changetime, product) V... ^ ---+--- Reporter: jav | Owner: jav Type: defect| Status: needinfo(new) Priority: blocker | Milestone: Component: multiproduct |Version: 0.6.0 Resolution:| Keywords: ---+--- Changes (by matevzb): * owner: nobody = jav * status: new = needinfo(new) Comment: This looks like a duplicate of #601, which has already been fixed on trunk. Could you please retry using the latest trunk build? -- Ticket URL: https://issues.apache.org/bloodhound/ticket/635#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #635: ProgrammingError: column product specified more than onceLINE 1: ...ne, component, version, keywords, cc, time, changetime, product) V... ^
#635: ProgrammingError: column product specified more than onceLINE 1: ...ne,component,version,keywords,cc,time,changetime, product) V... ^ ---+--- Reporter: jav | Owner: jav Type: defect| Status: needinfo(new) Priority: blocker | Milestone: Component: multiproduct |Version: 0.6.0 Resolution:| Keywords: ---+--- Comment (by jav): Sorry for the duplicate. Applying the patch from #601 worked. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/635#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #635: ProgrammingError: column product specified more than onceLINE 1: ...ne, component, version, keywords, cc, time, changetime, product) V... ^
#635: ProgrammingError: column product specified more than onceLINE 1: ...ne,component,version,keywords,cc,time,changetime, product) V... ^ ---+ Reporter: jav | Owner: Type: defect| Status: closed Priority: blocker | Milestone: Component: multiproduct |Version: 0.6.0 Resolution: duplicate | Keywords: ---+ Changes (by matevzb): * status: new = closed * resolution: = duplicate -- Ticket URL: https://issues.apache.org/bloodhound/ticket/635#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] New user registration: alice
New user registration for user alice -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #635: ProgrammingError: column product specified more than onceLINE 1: ...ne, component, version, keywords, cc, time, changetime, product) V... ^
#635: ProgrammingError: column product specified more than onceLINE 1: ...ne,component,version,keywords,cc,time,changetime, product) V... ^ ---+ Reporter: jav | Owner: Type: defect| Status: closed Priority: blocker | Milestone: Component: multiproduct |Version: 0.6.0 Resolution: duplicate | Keywords: ---+ Comment (by olemis): Replying to [comment:2 jav]: Sorry for the duplicate. Applying the patch from #601 worked. @jav : do not be sorry , we should have been released a new version already to avoid these situations (i.e. users experiencing the same issues already fixed in /trunk) . OTOH , the delay also means that a few more important enhancements will be included in forthcoming bug fix release . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/635#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #630: No relations types after upgrading 0.5.3 instance
#630: No relations types after upgrading 0.5.3 instance +-- Reporter: olemis | Owner: matevzb Type: defect | Status: accepted Priority: major | Milestone: Component: relations |Version: 0.6.0 Resolution: | Keywords: upgrade +-- Comment (by olemis): Replying to [comment:5 astaric]: It is enabled in new installations, as bloodhound_setup takes care of that. ... and it shall continue that way ... There is no obvious way to enable it on upgrade, as it is performed using trac-admin upgrade, which only upgrades already enabled modules. ;) We could hack the environment upgrade participant of one of the existing component, - but I do not think that is a good idea. + If number of modules included by default will keep increasing, we might consider adding --upgrade switch to the bloodhound_setup and then using the script to upgrade from one version to another. \o/ excellent idea ! -- Ticket URL: https://issues.apache.org/bloodhound/ticket/630#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
svn commit: r1513214 - /bloodhound/trunk/bloodhound_multiproduct/setup.py
Author: rjollos Date: Mon Aug 12 18:20:19 2013 New Revision: 1513214 URL: http://svn.apache.org/r1513214 Log: `multiproduct.batch` was not defined as an entry point for the `bloodhound_multiproduct` plugin, so it was being discovered as a single-file plugin. Refs #596. This is similar to the issue resolved in #582. Modified: bloodhound/trunk/bloodhound_multiproduct/setup.py Modified: bloodhound/trunk/bloodhound_multiproduct/setup.py URL: http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_multiproduct/setup.py?rev=1513214r1=1513213r2=1513214view=diff == --- bloodhound/trunk/bloodhound_multiproduct/setup.py (original) +++ bloodhound/trunk/bloodhound_multiproduct/setup.py Mon Aug 12 18:20:19 2013 @@ -46,6 +46,7 @@ setup( 'multiproduct.model = multiproduct.model', 'multiproduct.perm = multiproduct.perm', 'multiproduct.product_admin = multiproduct.product_admin', +'multiproduct.ticket.batch = multiproduct.ticket.batch', 'multiproduct.ticket.query = multiproduct.ticket.query', 'multiproduct.ticket.web_ui = multiproduct.ticket.web_ui', 'multiproduct.web_ui = multiproduct.web_ui',
Re: [Apache Bloodhound] #582: Relations widget component is displayed separate from Relations plugin on Plugin admin panel
#582: Relations widget component is displayed separate from Relations plugin on Plugin admin panel +--- Reporter: rjollos| Owner: rjollos Type: defect | Status: closed Priority: minor | Milestone: Release 7 Component: relations |Version: 0.5.3 Resolution: fixed | Keywords: +--- Comment (by rjollos): This `setup.py` problem described and then fixed in this ticket is causing the ''Unknown widget !TicketRelations'' warning on the ticket page with Release 0.6.0. We wouldn't have noticed this when installing plugins ijn dev mode because of the symbolic linking to the plugin source, but the issue is readily reproducible when installing the eggs normally. For reference, here are the two mailing list threads where the issue was discussed: * [http://markmail.org/message/6y2i5gjeo4qi7z5b] * [http://markmail.org/message/zifmtl6gumkm3aue] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/582#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] BloodhoundReleaseProcess modified
Page BloodhoundReleaseProcess was changed by rjollos Diff URL: https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess?action=diffversion=41 Revision 41 Comment: Note availability of old releases. Changes: ---8--8--8--8--8--8--8--8 Index: BloodhoundReleaseProcess = --- BloodhoundReleaseProcess (version: 40) +++ BloodhoundReleaseProcess (version: 41) @@ -150,7 +150,7 @@ 1. Update other locations that mention a specific release: 1. https://issues.apache.org/bloodhound/wiki/WikiStart (Download link and text) 1. http://bloodhound.apache.org/ - edit: https://svn.apache.org/repos/asf/bloodhound/site/index.html - 1. Remove the old release from https://dist.apache.org/repos/dist/release/bloodhound. + 1. Remove the old release from https://dist.apache.org/repos/dist/release/bloodhound. The old releases can be found on the [http://archive.apache.org/dist/bloodhound/ archive site]. 1. Edit the [/roadmap milestone] and mark it as //Completed//. 1. Add an entry for the release to the ticket //Version// enum through the [/admin/ticket/version administration page]. ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'BloodhoundReleaseProcess' page. If it was not you, please report to .
svn commit: r1513332 - in /bloodhound/trunk/bloodhound_relations/bhrelations: templates/manage.html templates/relations_manage.html web_ui.py
Author: rjollos Date: Tue Aug 13 03:48:27 2013 New Revision: 1513332 URL: http://svn.apache.org/r1513332 Log: Renamed `bhrelations` `manage.html` template so that it is more likely to be unique when plugins are installed. Added: bloodhound/trunk/bloodhound_relations/bhrelations/templates/relations_manage.html - copied unchanged from r1513331, bloodhound/trunk/bloodhound_relations/bhrelations/templates/manage.html Removed: bloodhound/trunk/bloodhound_relations/bhrelations/templates/manage.html Modified: bloodhound/trunk/bloodhound_relations/bhrelations/web_ui.py Modified: bloodhound/trunk/bloodhound_relations/bhrelations/web_ui.py URL: http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_relations/bhrelations/web_ui.py?rev=1513332r1=1513331r2=1513332view=diff == --- bloodhound/trunk/bloodhound_relations/bhrelations/web_ui.py (original) +++ bloodhound/trunk/bloodhound_relations/bhrelations/web_ui.py Tue Aug 13 03:48:27 2013 @@ -115,7 +115,7 @@ class RelationManagementModule(Component key=lambda x: x[0]), 'relations': self.get_ticket_relations(ticket), }) -return 'manage.html', data, None +return 'relations_manage.html', data, None # ITemplateProvider methods def get_htdocs_dirs(self):
Re: [Apache Bloodhound] #523: Implement Bloodhound Relation management page
#523: Implement Bloodhound Relation management page --+--- Reporter: andrej | Owner: matevzb Type: enhancement | Status: closed Priority: major| Milestone: Release 6 Component: relations|Version: Resolution: fixed| Keywords: --+--- Comment (by rjollos): Replying to [comment:8 rjollos]: Trac requires that each template have a unique name, so I would suggest the following change ... Committed in [1513332]. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/523#comment:9 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
