Custom Query (332 matches)


Show under each result:

Results (28 - 30 of 332)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Ticket Resolution Summary Owner Reporter
#227 fixed [patch] allow '_' in inline properties bas thomas.moschny@…

The subject already says it. Is there a reason to not allow some more characters, especially '_' for the name of inline properties? We have custom fields which contain them, and I want people to be able to set these fields via mail.

#228 fixed clearing ticket fields via inline properties doesn't work bas thomas.moschny@…

Expected to be able to clear ticket fields by using empty inline properties, like this:


but that doesn't work, the field contents isn't cleared. (Trac 0.11.7, email2trac r492)

Seems this is explicitly checked here. Is there a reason for that check?

#277 fixed "database locked" issue bas thomas.moschny@…

I thought I'd ask per mail first, before creating a ticket; maybe this
is a (configuration) error on our side, or something like that.

Here's the issue: Occasionally we lose mails in our email2trac -> Trac
setup, and get trackbacks like this in the syslog:

Oct 26 11:35:00 <hostname> email2trac <prjname>: subject: u'#4951: XXX'
Oct 26 11:35:11 <hostname> email2trac <prjname>: Traceback (most recent call
Oct 26 11:35:11 <hostname> email2trac <prjname>:   File
"/opt/trac/bin/email2trac", line 2553, in ?     tktparser.parse(sys.stdin)
Oct 26 11:35:11 <hostname> email2trac <prjname>:   File
"/opt/trac/bin/email2trac", line 1689, in parse     if not
self.ticket_update(m,'reply')[:-1], spam_msg):
Oct 26 11:35:11 <hostname> email2trac <prjname>:   File
"/opt/trac/bin/email2trac", line 985, in ticket_update
tkt.save_changes(, body_text, when, None, str(cnum))
Oct 26 11:35:11 <hostname> email2trac <prjname>:   File
packages/Trac-0.11.8dev_r10236-py2.4.egg/trac/ticket/", line 293, in
save_changes     db.commit()
Oct 26 11:35:11 <hostname> email2trac <prjname>:   File
"/usr/lib64/python2.4/site-packages/sqlite/", line 540, in commit
Oct 26 11:35:11 <hostname> email2trac <prjname>: OperationalError: database
is locked

As you can see, we are using Python 2.4 (well, we are on Centos5),
Trac 0.11.8dev and email2trac 2.4.0 (I know there's a later version,
will try it, but couldn't find anything relevant in the changelog).

It seems clear that email2trac might not be causing the issue, but is
suffering from it: something else might be blocking the DB while
email2trac tries to insert or update a ticket.

So the question is: Can email2trac repeat and try again for a while, or
else save the message somewhere so it doesn't get lost?

Best regards,
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Note: See TracQuery for help on using queries.