OperationalError: near ",": syntax error

Trac detected an internal error:
OperationalError: near ",": syntax error
This is probably a local installation issue.

Found a bug in Trac?

If you think this should work and you can reproduce the problem, you should consider creating a bug report.

Note that the Trac-jsGantt plugin seems to be involved. Please report this issue to the plugin maintainer.

Before you do that, though, please first try searching for similar issues, as it is quite likely that this problem has been reported before. For questions about installation and configuration of Trac or its plugins, please try the mailing list instead of creating a ticket.

Otherwise, please a new bug report describing the problem and explain how to reproduce it.

Python Traceback

Most recent call last:

File "/usr/local/lib/python2.6/dist-packages/Trac-1.0.1-py2.6.egg/trac/web/main.py", line 497, in _dispatch_request
File "/usr/local/lib/python2.6/dist-packages/Trac-1.0.1-py2.6.egg/trac/web/main.py", line 214, in dispatch
File "/usr/local/lib/python2.6/dist-packages/Trac-1.0.1-py2.6.egg/trac/ticket/web_ui.py", line 180, in process_request
File "/usr/local/lib/python2.6/dist-packages/Trac-1.0.1-py2.6.egg/trac/ticket/web_ui.py", line 465, in _process_newticket_request
File "/usr/local/lib/python2.6/dist-packages/Trac-1.0.1-py2.6.egg/trac/ticket/web_ui.py", line 1289, in _do_create
File "/usr/local/lib/python2.6/dist-packages/Trac-1.0.1-py2.6.egg/trac/ticket/model.py", line 256, in insert
File "/usr/local/lib/python2.6/dist-packages/Trac_jsGantt-0.10_r12998-py2.6.egg/tracjsgantt/tracpm.py", line 2943, in ticket_created

Just to let you know, having the same issue as of today for some reason. I get the issue upon updating tickets blockedby attribute. Using sqlite3 db. If i disable ticketrescheduler the problem goes away. Re-enabling the ticketrescheduler and the problem comes back.

I'm aware that I have some crap data in the custom fields (some users are not aware of limitations such as not using ~ in remaining time and so forth and there is no sanitation of this data). Could this be affecting?

Actually, I think it may be a related problem but not the same. Enabling/Disabling the ticketRescheduler does fix the issue, but stack trace is different, and it happens on updates. Created a separate ticket for my issue at #11139

Just spun up a new development server on CentOS 6.4 and used the epel Trac 0.12.5-1 release, same as our previous development server. Some of the other plugins upgraded, so moved to newer versions of TracMasterTickets, SubTickets, DateField and Burndown and what-the-heck I updated jsGantt to 0.10-r12899 I think it was (even though the svn tree says 0.11)

Had this exact error and tried updating the config settings for jsGantt plugin but no dice. Simply reverting to the previous release I installed earlier this year r12565 fixed the problem with no configuration changes required.

I am going to agree with a previous poster that the problem is like SQL query related with a variable typo or incomplete migration to new variable name or structure.

Any way, it certainly looks like a code rev between r12565 and latest introduced this buggy behavior related to the rescheduling operation.

Add Comment

This ticket has been modified since you started editing. You should review the
other modifications which have been appended above,
and any conflicts shown in the preview below.
You can nevertheless proceed and submit your changes if you wish so.