Custom Query (332 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (256 - 258 of 332)

Ticket Resolution Summary Owner Reporter
#202 fixed email2trac does not honor Trac permissions when creating/updating tickets bas Dennis McRitchie <dmcr@…>
Description

Hi Bas,

I love this script, and am increasingly using it with our Trac projects; however, one problem is that it does not appear to respect the Trac permissions set up for creating or updating tickets.

This seems to happen whether the reporter is "anonymous" (in which case, I would expect it to respect the permissions assigned to "anonymous"), as well as when the reporter has an email address that can be translated into one of the known users (where I would expect email2trac to respect the permissions for that user).

As it is, email2trac will create a ticket for anyone, even if that person could not create a ticket if they went to the Trac website and tried to do it from there. I would think the two methods should be consistent.

Is this intentional, or just something you have not had time to get around to yet? Or worse still, does Trac not support a way of finding out the permissions using its API?

Thanks,

Dennis

P.S. I'm actually using 1.4.2, which is not on the Version drop-down list.

#428 invalid email2trac crashes with Python error bas anonymous
Description

When running email2trac 2.12.2 on CentOS7 with Python 2.7.5 and the commandline:

email2trac -d -v < msg.txt

using the msg.txt distributed with the application, parsing crashes. python does a trace dump as follows:

2018-05-06 16:54:59,457 email2trac test: function inline_properties 2018-05-06 16:54:59,457 email2trac test: function unique_attachment_names() 2018-05-06 16:54:59,457 email2trac test: function get_body_text() 2018-05-06 16:54:59,459 email2trac test: Traceback (most recent call last):

2018-05-06 16:54:59,459 email2trac test: File "/usr/local/bin/email2trac", line 2922, in <module>

tktparser.parse(sys.stdin)

2018-05-06 16:54:59,459 email2trac test: File "/usr/local/bin/email2trac", line 1863, in parse

self.parse_subject_field(m, subject, spam_msg)

2018-05-06 16:54:59,459 email2trac test: File "/usr/local/bin/email2trac", line 2008, in parse_subject_field

self.new_ticket(m, subject, spam_msg)

2018-05-06 16:54:59,459 email2trac test: File "/usr/local/bin/email2trac", line 1340, in new_ticket

self.id = tkt.insert()

2018-05-06 16:54:59,459 email2trac test: File "/usr/lib64/python2.7/site-packages/trac/ticket/model.py", line 261, in insert

db_values = self._to_db_types(self.values)

2018-05-06 16:54:59,459 email2trac test: File "/usr/lib64/python2.7/site-packages/trac/ticket/model.py", line 405, in _to_db_types

values[field] = _datetime_to_db_str(value, is_custom_field)

2018-05-06 16:54:59,460 email2trac test: File "/usr/lib64/python2.7/site-packages/trac/ticket/model.py", line 63, in _datetime_to_db_str

ts = to_utimestamp(dt)

2018-05-06 16:54:59,460 email2trac test: File "/usr/lib64/python2.7/site-packages/trac/util/datefmt.py", line 193, in to_utimestamp

diff = dt - _epoc

2018-05-06 16:54:59,460 email2trac test: TypeError?: unsupported operand type(s) for -: 'unicode' and 'datetime.datetime'

2018-05-06 16:54:59,460 email2trac test: saving email to /tmp/test_DeEDc.email2trac 2018-05-06 16:54:59,461 email2trac test: function get_message_parts() 2018-05-06 16:54:59,461 email2trac test: Message part: Main-Type: multipart 2018-05-06 16:54:59,461 email2trac test: Message part: Content-Type: multipart/mixed 2018-05-06 16:54:59,461 email2trac test: Skipping multipart container 2018-05-06 16:54:59,461 email2trac test: Message part: Main-Type: text 2018-05-06 16:54:59,461 email2trac test: Message part: Content-Type: text/plain

#205 fixed email2trac chokes on non-ascii (utf8) characters in workflow bas eirik.schwenke@…
Description

We had an initial ticket status of "forespørsel", and that caused email2trac to fail with the error(s):

email2trac: Traceback (most recent call last): 
email2trac:   File "/usr/bin/email2trac", line 2133, in <module>     tktparser.parse(sys .stdin) 
email2trac:   File "/usr/bin/email2trac", line 1531, in parse     self.new_ticket(m, sub ject, spam_msg) 
email2trac:   File "/usr/bin/email2trac", line 967, in new_ticket     self.set_ticket_fi elds(tkt) 
email2trac:   File "/usr/bin/email2trac", line 876, in set_ticket_fields     print 'trac .ini name %s = %s' %(name, value) 
email2trac: UnicodeEncodeError: 'ascii' codec can't encode character u'\xf8' in position 27: ordinal not in range(128) 

It would appear some more care is needed to support unicode in all strings in email2trac. I had a brief look at the script, but couldn't easily see if it would be safe and sound to simply wrap all missing strings with a .encode('utf-8') or not.

For now the workaround has been to limit ourselves to ascii-characters in ticket-status names -- but that is obviously not a good solution (it's looks a bit strange in Norwegian, in eg. Japanese it would be hopeless).

Note: See TracQuery for help on using queries.