Strange `database is locked` error: commit fails but data is nevertheless saved...
|Reported by:||Christian Boos||Owned by:||Jonas Borgström|
|Severity:||normal||Keywords:||database lock pysqlite weird|
I just tried to close #3410, and I got the following error message:
Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 314, in dispatch_request dispatcher.dispatch(req) File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 199, in dispatch resp = chosen_handler.process_request(req) File "/usr/lib/python2.3/site-packages/trac/ticket/web_ui.py", line 260, in process_request self._do_save(req, db, ticket) File "/usr/lib/python2.3/site-packages/trac/ticket/web_ui.py", line 530, in _do_save db.commit() OperationalError: database is locked
So far so good (well…) but when looking at the timeline immediately after that, the change appears to have succeeded! And that's really puzzling: if the commit fails, the data shouldn't persist.
This is not the first time I see somthing like this, so now I've decided to create a ticket about it. No milestone set, it's just a place to record the issue and discuss it until what happens is understood…
Change History (8)
comment:6 by , 13 years ago
|Priority:||low → normal|
|Status:||closed → reopened|