#6074 closed defect (wontfix)
Bug during custom filters
Reported by: | Owned by: | Christopher Lenz | |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | roadmap | Version: | 0.10.4 |
Severity: | minor | Keywords: | clearsilver |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
At the pycon-tech trac https://pycon.coderanger.net/ I try to filter by:
new, assigned, reopened priority is not minor, trivial group by milestone
and I get this error (I did it twice to be sure)
Traceback (most recent call last): File "/var/lib/python-support/python2.5/trac/web/main.py", line 406, in dispatch_request dispatcher.dispatch(req) File "/var/lib/python-support/python2.5/trac/web/main.py", line 237, in dispatch resp = chosen_handler.process_request(req) File "/var/lib/python-support/python2.5/trac/ticket/query.py", line 443, in process_request self.display_html(req, query) File "/var/lib/python-support/python2.5/trac/ticket/query.py", line 609, in display_html req.hdf['query.num_matches_group'] = num_matches_group File "/var/lib/python-support/python2.5/trac/web/clearsilver.py", line 197, in __setitem__ self.set_value(name, value, True) File "/var/lib/python-support/python2.5/trac/web/clearsilver.py", line 245, in set_value add_value(name, value) File "/var/lib/python-support/python2.5/trac/web/clearsilver.py", line 237, in add_value add_value('%s.%s' % (prefix, k), value[k]) File "/var/lib/python-support/python2.5/trac/web/clearsilver.py", line 244, in add_value set_str(prefix, value) File "/var/lib/python-support/python2.5/trac/web/clearsilver.py", line 215, in set_str self.hdf.setValue(prefix.encode('utf-8'), str(value)) Error: Traceback (innermost last): File "neo_hdf.c", line 805, in hdf_set_value() File "neo_hdf.c", line 795, in _set_value() AssertError: Unable to set Empty component query.num_matches_group._Schedule Mgmt.. System_
Attachments (0)
Change History (4)
comment:1 by , 17 years ago
Version: | → 0.10.4 |
---|
comment:2 by , 17 years ago
Component: | general → roadmap |
---|---|
Description: | modified (diff) |
Keywords: | clearsilver added |
Milestone: | → 0.10.5 |
Owner: | changed from | to
Priority: | normal → low |
Severity: | normal → minor |
Well, it's a valid defect for 0.10, so perhaps we should keep it open for 0.10.5 until either someone contributes a patch or we drop maintenance of 0.10-stable.
comment:3 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
It seems we'll drop maintenance of 0.10-stable before this will ever get fixed.
Of course, if someone wants to share a fix for this bug, he's more than welcome to provide a (well tested) patch and reopen the ticket.
comment:4 by , 17 years ago
Milestone: | 0.10.5 |
---|
Looks like the problem is just that the milestone name has a '.', which makes clearsilver explode. Should we close this as a won't fix since 0.11dev shouldn't be affected?