[Apache Bloodhound] #666: On the WebAdmin Permissions panel, invalid permissions should be styled differently

2013-09-24 Thread Apache Bloodhound
#666: On the WebAdmin Permissions panel, invalid permissions should be styled
differently
-+-
 Reporter:  rjollos  |  Owner:  rjollos
 Type:  enhancement  | Status:  new
 Priority:  major|  Milestone:
Component:  ui design|Version:
 Keywords:  trac-1.0.0   |
-+-
 Changes from trac:#10752 should be incorporated into !BloodhoundTheme.

-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/666
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker


Re: [Apache Bloodhound] #667: Error rendering forbidden pages

2013-09-24 Thread Apache Bloodhound
#667: Error rendering forbidden pages
+-
  Reporter:  olemis |  Owner:  nobody
  Type:  defect | Status:  new
  Priority:  blocker|  Milestone:  Release 8
 Component:  ui design  |Version:  0.7.0
Resolution: |   Keywords:  permissions, chrome
+-
Changes (by olemis):

 * component:   = ui design
 * priority:  major = blocker
 * owner:   = nobody
 * version:   = 0.7.0
 * milestone:   = Release 8
 * keywords:   = permissions, chrome


-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/667#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker


[Apache Bloodhound] #667: Error rendering forbidden pages

2013-09-24 Thread Apache Bloodhound
#667: Error rendering forbidden pages
-+---
  Reporter:  olemis  |Owner:
  Type:  defect  |   Status:  new
  Priority:  major   |  Version:
Resolution:  |
-+---
  How to Reproduce 

 While doing a GET operation on `/query`, Trac issued an internal error.

 Initially the web page was loaded as expected . The error message was
 displayed after revoking permissions to view target resource.

 Request parameters:
 {{{
 {}
 }}}

 User agent: Chromium 17.0.963.79 (Developer Build 125985 Linux) Ubuntu
 10.04

  System Information 
 ''System information not available''

  Enabled Plugins 
 ''Plugin information not available''

  Python Traceback 
 {{{
 Traceback (most recent call last):
   File /path/to/bloodhound/trac/trac/web/main.py, line 477, in
 _dispatch_request
 dispatcher.dispatch(req)
   File /path/to/bloodhound/trac/trac/web/main.py, line 179, in dispatch
 chosen_handler)
   File /path/to/bloodhound/trac/trac/web/main.py, line 325, in
 _pre_process_request
 chosen_handler = filter_.pre_process_request(req, chosen_handler)
   File /path/to/bloodhound/bloodhound_theme/bhtheme/theme.py, line 256,
 in pre_process_request
 for i, entry in enumerate(req.chrome['nav']['mainnav']):
 KeyError: 'mainnav'
 }}}

-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/667
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker


[Apache Bloodhound] #668: Negative integers for ticket IDs

2013-09-24 Thread Apache Bloodhound
#668: Negative integers for ticket IDs
-+-
  Reporter:  olemis  |Owner:
  Type:  defect  |   Status:  new
  Priority:  major   |  Version:  0.7.0
Resolution:  |
-+-
 In an environment (DB=postgresql) upgraded to work against 0.8-dev (i.e.
 current /trunk) I've executed an RPC request to invoke `ticket.create`
 method in batch (i.e. using `system.multicall`). The ticket IDs I got are
 all set to `-1` instead of expected positive integers in product-specific
 sequence. In the log s I also notice this error.

 [[span(Log entry, class=label label-success)]]
 {{{
 2013-09-24 07:54:53,489 Trac[ticket] ERROR: Failure sending notification
 on creation of ticket #-1: local variable 'reporter' referenced before
 assignment
 }}}

 [[span(Log entry, class=label label-success)]]
 {{{#!py
 Traceback (most recent call last):
   File /path/to/bloodhound_rpc/trunk/tracrpc/ticket.py, line 175, in
 create
 tn.notify(t, newticket=True)
   File /path/to/bloodhound/trac/trac/ticket/notification.py, line 156,
 in notify
 self._notify(ticket, newticket, modtime)
   File /path/to/bloodhound/trac/trac/ticket/notification.py, line 270,
 in _notify
 NotifyEmail.notify(self, ticket.id, subject, author)
   File /path/to/bloodhound/trac/trac/notification.py, line 344, in
 notify
 Notify.notify(self, resid)
   File /path/to/bloodhound/trac/trac/notification.py, line 230, in
 notify
 (torcpts, ccrcpts) = self.get_recipients(resid)
   File /path/to/bloodhound/trac/trac/ticket/notification.py, line 388,
 in get_recipients
 tktid, self.prev_cc)
   File /path/to/bloodhound/trac/trac/ticket/notification.py, line 129,
 in get_ticket_notification_recipients
 return (torecipients, ccrecipients, reporter, owner)
 UnboundLocalError: local variable 'reporter' referenced before assignment
 }}}

 This is working fine in my local working copy with an environment
 DB=sqlite .

-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/668
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker


Re: [Apache Bloodhound] #668: Negative integers for ticket IDs

2013-09-24 Thread Apache Bloodhound
#668: Negative integers for ticket IDs
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  Release 8
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  bep-0010
---+---
Changes (by olemis):

 * component:   = multiproduct
 * priority:  major = blocker
 * owner:   = nobody
 * version:  0.7.0 =
 * milestone:   = Release 8
 * keywords:   = bep-0010


Old description:

 In an environment (DB=postgresql) upgraded to work against 0.8-dev (i.e.
 current /trunk) I've executed an RPC request to invoke `ticket.create`
 method in batch (i.e. using `system.multicall`). The ticket IDs I got are
 all set to `-1` instead of expected positive integers in product-specific
 sequence. In the log s I also notice this error.

 [[span(Log entry, class=label label-success)]]
 {{{
 2013-09-24 07:54:53,489 Trac[ticket] ERROR: Failure sending notification
 on creation of ticket #-1: local variable 'reporter' referenced before
 assignment
 }}}

 [[span(Log entry, class=label label-success)]]
 {{{#!py
 Traceback (most recent call last):
   File /path/to/bloodhound_rpc/trunk/tracrpc/ticket.py, line 175, in
 create
 tn.notify(t, newticket=True)
   File /path/to/bloodhound/trac/trac/ticket/notification.py, line 156,
 in notify
 self._notify(ticket, newticket, modtime)
   File /path/to/bloodhound/trac/trac/ticket/notification.py, line 270,
 in _notify
 NotifyEmail.notify(self, ticket.id, subject, author)
   File /path/to/bloodhound/trac/trac/notification.py, line 344, in
 notify
 Notify.notify(self, resid)
   File /path/to/bloodhound/trac/trac/notification.py, line 230, in
 notify
 (torcpts, ccrcpts) = self.get_recipients(resid)
   File /path/to/bloodhound/trac/trac/ticket/notification.py, line 388,
 in get_recipients
 tktid, self.prev_cc)
   File /path/to/bloodhound/trac/trac/ticket/notification.py, line 129,
 in get_ticket_notification_recipients
 return (torecipients, ccrecipients, reporter, owner)
 UnboundLocalError: local variable 'reporter' referenced before assignment
 }}}

 This is working fine in my local working copy with an environment
 DB=sqlite .

New description:

 In an environment (DB=postgresql) upgraded to work against 0.8-dev (i.e.
 current /trunk) I've executed an RPC request to invoke `ticket.create`
 method in batch (i.e. using `system.multicall`). The ticket IDs I got are
 all set to `-1` instead of expected positive integers in product-specific
 sequence. In the logs I also notice this error.

 [[span(Log entry, class=label label-success)]]
 {{{
 2013-09-24 07:54:53,489 Trac[ticket] ERROR: Failure sending notification
 on creation of ticket #-1: local variable 'reporter' referenced before
 assignment
 }}}

 [[span(Traceback, class=label label-success)]]
 {{{#!py
 Traceback (most recent call last):
   File /path/to/bloodhound_rpc/trunk/tracrpc/ticket.py, line 175, in
 create
 tn.notify(t, newticket=True)
   File /path/to/bloodhound/trac/trac/ticket/notification.py, line 156,
 in notify
 self._notify(ticket, newticket, modtime)
   File /path/to/bloodhound/trac/trac/ticket/notification.py, line 270,
 in _notify
 NotifyEmail.notify(self, ticket.id, subject, author)
   File /path/to/bloodhound/trac/trac/notification.py, line 344, in
 notify
 Notify.notify(self, resid)
   File /path/to/bloodhound/trac/trac/notification.py, line 230, in
 notify
 (torcpts, ccrcpts) = self.get_recipients(resid)
   File /path/to/bloodhound/trac/trac/ticket/notification.py, line 388,
 in get_recipients
 tktid, self.prev_cc)
   File /path/to/bloodhound/trac/trac/ticket/notification.py, line 129,
 in get_ticket_notification_recipients
 return (torecipients, ccrecipients, reporter, owner)
 UnboundLocalError: local variable 'reporter' referenced before assignment
 }}}

 This is working fine in my local working copy with an environment
 DB=sqlite .

--

-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/668#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker


Re: [Apache Bloodhound] #667: Error rendering forbidden pages

2013-09-24 Thread Apache Bloodhound
#667: Error rendering forbidden pages
+-
  Reporter:  olemis |  Owner:  rjollos
  Type:  defect | Status:  accepted
  Priority:  blocker|  Milestone:  Release 8
 Component:  ui design  |Version:  0.7.0
Resolution: |   Keywords:  permissions, chrome
+-
Changes (by rjollos):

 * owner:  nobody = rjollos
 * status:  new = accepted


Comment:

 I suppose it is a regression from r1522789. I will take a look.

-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/667#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker


[Apache Bloodhound] #669: Edit product link - after #562

2013-09-24 Thread Apache Bloodhound
#669: Edit product link - after #562
-+---
  Reporter:  olemis  |Owner:
  Type:  defect  |   Status:  new
  Priority:  major   |  Version:
Resolution:  |
-+---
 In products list there is no evident navigation item to edit product
 fields.

-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/669
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker


[Apache Bloodhound] #670: Relation type is empty

2013-09-24 Thread Apache Bloodhound
#670: Relation type is empty
-+---
  Reporter:  olemis  |Owner:
  Type:  defect  |   Status:  new
  Priority:  major   |  Version:
Resolution:  |
-+---
 If a ticket is connected to many others and same relation type is
 specified more than once (different ticket IDs) then values in cells for
 ''relation type'' will be empty .

-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/670
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker


[Apache Bloodhound] #672: Edit ticket relationships

2013-09-24 Thread Apache Bloodhound
#672: Edit ticket relationships
--+---
  Reporter:  olemis   |Owner:
  Type:  enhancement  |   Status:  new
  Priority:  major|  Version:
Resolution:   |
--+---
 It's not possible to edit relation comments. The only choice is to delete
 it and recreate it once again , which is annoying .

-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/672
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker


Re: [Apache Bloodhound] #672: Edit ticket relationships

2013-09-24 Thread Apache Bloodhound
#672: Edit ticket relationships
--+
  Reporter:  olemis   |  Owner:  nobody
  Type:  enhancement  | Status:  new
  Priority:  minor|  Milestone:
 Component:  relations|Version:  0.7.0
Resolution:   |   Keywords:  crud
--+
Changes (by olemis):

 * owner:   = nobody
 * keywords:   = crud
 * version:   = 0.7.0
 * component:   = relations
 * priority:  major = minor


-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/672#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker


Re: [Apache Bloodhound] #670: Relation type is empty

2013-09-24 Thread Apache Bloodhound
#670: Relation type is empty
+
  Reporter:  olemis |  Owner:  nobody
  Type:  defect | Status:  new
  Priority:  critical   |  Milestone:
 Component:  relations  |Version:
Resolution: |   Keywords:
+
Changes (by olemis):

 * owner:   = nobody
 * priority:  major = critical
 * component:   = relations


-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/670#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker


Re: [Apache Bloodhound] #669: Edit product link - after #562

2013-09-24 Thread Apache Bloodhound
#669: Edit product link - after #562
---+
  Reporter:  olemis|  Owner:  olemis
  Type:  defect| Status:  accepted
  Priority:  critical  |  Milestone:  Release 8
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  product, crud, nav
---+
Changes (by olemis):

 * status:  new = accepted
 * component:   = multiproduct
 * priority:  major = critical
 * owner:   = olemis
 * milestone:   = Release 8
 * keywords:   = product, crud, nav


-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/669#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker


Re: [Apache Bloodhound] #671: Product edits always reported as anonymous

2013-09-24 Thread Apache Bloodhound
#671: Product edits always reported as anonymous
---+---
  Reporter:  olemis|  Owner:  olemis
  Type:  defect| Status:  accepted
  Priority:  minor |  Milestone:
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  product, crud
---+---
Changes (by olemis):

 * keywords:   = product, crud
 * priority:  major = minor
 * status:  new = accepted
 * component:   = multiproduct
 * owner:   = olemis


-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/671#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker


Re: [Apache Bloodhound] #669: Edit product link - after #562

2013-09-24 Thread Apache Bloodhound
#669: Edit product link - after #562
---+
  Reporter:  olemis|  Owner:
  Type:  defect| Status:  review
  Priority:  critical  |  Milestone:  Release 8
 Component:  multiproduct  |Version:
Resolution:|   Keywords:  product, crud, nav
---+
Changes (by olemis):

 * owner:  olemis =
 * status:  accepted = review


Comment:

 The patch in attachment:t669_r1525378_product_edit.diff adds edit link for
 products and tweaks hooks implementation in order to correctly process
 such requests (which seemed to be impossible to do). In my local working
 copy it worked by applying it against r1525325 .

 The second patch delivers functional test cases for this feature . It
 requires quite a few more patches listed below

 {{{#!sh

 $ hg qapplied
 t387/t387_r1487712_bloodhound_setup.diff
 t387/t387_r1485255_functional_test_infra.diff
 t387/t387_r1495238_attach_btn_value.diff
 t387/t387_r1495238_functional_test.2.diff
 t387/t387_r1495238_functional_test.3.diff
 t387/t387_r1514232_functional_test.4.diff
 t387/t387_r1514860_functional_test.5.diff
 t598/t598_r1510975_functional_tester_product.diff
 t387/t387_r1515319_functional_test.6.diff
 t387/t387_r1515319_functional_test.7.diff
 t598/t598_r1510975_new_product_intertracwiki.diff
 t598/t598_r1510975_test_new_product.diff
 t669/t669_r1525378_product_edit.diff
 t669/t669_r1525378_product_edit.tests.diff

 $ hg log -r qparent
 changeset:   444:1b7d2c0e51b1
 tag: qparent
 tag: svn-1525325
 user:rjollos@13f79535-47bb-0310-9956-ffa450edef68
 date:Sun Sep 22 06:21:50 2013 +
 summary: 0.8dev: PEP-0008 whitespace changes.

 }}}

-- 
Ticket URL: https://issues.apache.org/bloodhound/ticket/669#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker