Modify ↓
Opened 14 years ago
Closed 7 years ago
#8120 closed defect (wontfix)
UserChangeSubscriber causes “tuple index out of range” errors
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | AnnouncerPlugin |
Severity: | critical | Keywords: | |
Cc: | Trac Release: | 0.12 |
Description
2010-11-21 19:53:46,537 Trac[api] ERROR: AnnouncementSystem failed. Traceback (most recent call last): File "/usr/local/lib/python2.6/dist-packages/TracAnnouncer-0.12.1.dev-py2.6.egg/announcer/api.py", line 536, in _real_send subscriptions = self.resolver.subscriptions(evt) File "/usr/local/lib/python2.6/dist-packages/TracAnnouncer-0.12.1.dev-py2.6.egg/announcer/api.py", line 354, in subscriptions ordered_subs = sorted(subscriptions, key=itemgetter(1,2,3,6)) IndexError: tuple index out of range
It appears that UserChangeSubscriber is, at least sometimes, returning tuples that are only 4 items long. I am not entirely clear on why (or how) this is happening. In looking at the data stored in the subscription_attribute table, “target” is always blank, so I am not entirely sure that this subscriber isn’t simply broken.
Attachments (0)
Change History (4)
comment:1 Changed 14 years ago by
comment:2 Changed 12 years ago by
Owner: | changed from Robert Corsaro to Steffen Hoffmann |
---|
comment:3 Changed 8 years ago by
Owner: | Steffen Hoffmann deleted |
---|
comment:4 Changed 7 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Please upgrade to Trac 1.2, which has integrated the core of AnnouncerPlugin. Please raise the issue on the trac:MailingList if you encounter the issue with Trac 1.2.
Note: See
TracTickets for help on using
tickets.
This issue continued to occur even after UserChangeSubscriber was disabled. I have no idea what‘s going on here, and have resorted to filtering out any tuples that are shorter than they are supposed to be by changing
[x for x in sp.matches(event) if x]
to[x for x in sp.matches(event) if x and len(x) > 6]
inSubscriptionResolver.subscriptions
.