replybot does not handle SQLite database locked concurrency well
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Python Replybot |
In Progress
|
High
|
Unassigned |
Bug Description
Poorly formatted, but replybot can fail when committing the transaction if the
SQLite database is already locked.
Command died with
status 1: "/usr/bin/replybot -s xxx". Command output: Traceback (most
recent call last): File "/usr/bin/
load_
"build/
"build/
File
"/usr/
line 105, in commit self.flush() File
"/usr/
line 443, in flush self._flush_
"/usr/
line 502, in _flush_one self._connectio
File
"//usr/
line 202, in execute self.raw_execute, statement, params) File
"//usr/
line 317, in _check_disconnect return function(*args, **kwargs) File
"/usr/
line 153, in raw_execute return Connection.
params) File
"//usr/
line 283, in raw_execute raw_cursor.
sqlite3.
Changed in replybot: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in replybot: | |
status: | Triaged → In Progress |
milestone: | none → 5.1.0 |