Custom query (902 matches)


Show under each result:

Results (106 - 108 of 902)

Ticket Resolution Summary Owner Reporter
#1198 fixed email2trac borked llynch@… sra@…

Jen Linkova reported problems creating tickets via email. Both Lucy and I had some trouble reproducing, but that appears to be because of the twisty maze, not because it's not a real error. email2trac bombs:

<>: Command died with status 1:
    "/usr/local/bin/run_email2trac --project=noc"

Cranking up logging in /usr/local/etc/email2trac.conf eventually yielded a backtrace:

Traceback (most recent call last):
  File "/usr/local/bin/email2trac", line 2955, in <module>
  File "/usr/local/bin/email2trac", line 1864, in parse
    self.parse_subject_field(m, subject, spam_msg)
  File "/usr/local/bin/email2trac", line 1960, in parse_subject_field
    elif not self.ticket_update(m,'reply')[:-1], spam_msg):
  File "/usr/local/bin/email2trac", line 1129, in ticket_update
    tkt.save_changes(, body_text, when, None, str(cnum))
  File "/usr/local/lib/python2.7/site-packages/trac/ticket/", line 390, in save_changes
    """, (, when_ts, author, cnum, comment))
  File "/usr/local/lib/python2.7/site-packages/trac/db/", line 155, in __exit__
OperationalError: disk I/O error

Not sure what that's about yet, might be a strange way of saying "permission error". Most likely induced by an upgrade, as usual, but that's just conjecture.

#1197 fixed not enough power at chair tables mtd@… lee@…

I'm in Collyer now, but it was true in whatever other meeting room we used: there's only one available power outlet at the table. With three chairs, we're in contention for that outlet, and my machine won't make it through the full WG meeting without power.

We pulled a power strip from the front row, so this is either a request to backfill that strip, or to provision more outlets at the chair tables at future meetings.

#1196 worksforme testing < default > llynch@…
based on report
Note: See TracQuery for help on using queries.