"poisoned lock: another task failed inside" #405
Comments
|
Ouch, so sorry about this. Can you try a pre-release like v0.12.3b6? It is possible that the underlying bug has been fixed since v0.12.2. Note Unfortunately, v0.12.3b7 and v0.12.3b8 have issues on windows: ActivityWatch/activitywatch#936, caused by me being overly eager to upgrade Python version used for building in ActivityWatch/activitywatch#931. |
|
With v0.12.2, running With v0.12.3b6, I got a different result (but still unexpected). "Timeline" still works, but "Activity" still doesn't -- it outputs a subset of my activity for one specific day (yesterday), and "no data" for all other days. Secondly, no more rust lock errors in logs: The verbose flag |
I tried some more times, and am currently not sure if starting with the verbose flag can actually solve the problem. Now it doesn't work anymore. |
|
If it doesn't work with 0.12.3b7, can you run aw-server-rust with the environment variable RUST_BACKTRACE=1 set? You might need to run it outside of aw-qt also to get the backtrace. |
|
With This happens before the log |
|
Just for your info, I currently three watchers -- stock I have exported data generated by my own watcher, and found that it contains overlapping reports like: Expand JSON[
{
"id": 902212,
"timestamp": "2023-08-29T15:49:18.529Z",
"duration": 30.014,
"data": { "status": "not-afk" }
},
{
"id": 901517,
"timestamp": "2023-08-29T14:32:49.530Z",
"duration": 4255.686,
"data": { "status": "not-afk" }
},
{
"id": 901511,
"timestamp": "2023-08-29T14:14:24.144Z",
"duration": 60.004912,
"data": { "status": "afk" }
},
{
"id": 901512,
"timestamp": "2023-08-29T14:14:24.143Z",
"duration": 1105.386,
"data": { "status": "afk" }
},
{
"id": 900405,
"timestamp": "2023-08-29T11:58:31.905Z",
"duration": 8152.238,
"data": { "status": "not-afk" }
},
{
"id": 900397,
"timestamp": "2023-08-29T11:13:05.428Z",
"duration": 60.005447,
"data": { "status": "afk" }
},
{
"id": 900398,
"timestamp": "2023-08-29T11:13:05.427Z",
"duration": 2726.477,
"data": { "status": "afk" }
}
]However, the official Expand JSON[
{
"id": 713091,
"timestamp": "2023-07-16T04:04:25.551Z",
"duration": 192.519,
"data": {
"status": "afk"
}
},
{
"id": 713092,
"timestamp": "2023-07-16T04:04:25.540Z",
"duration": 25935.54,
"data": {
"status": "afk"
}
},
{
"id": 713089,
"timestamp": "2023-07-16T04:03:38.032Z",
"duration": 47.518,
"data": {
"status": "not-afk"
}
}
]That's just my observation. I'm not sure if this will mess up with sorting and merging periods. |
I'm using the latest release of AW (0.12.2) on Windows 11 (22H2 build 22621.2215) with
aw-server-rustenabled. Lately whenever I open up the web UI and check any day under "activity" I got this in the logs foraw-server-rust:The same warning (
Taking datastore lock failed, returning 504: poisoned lock: another task failed inside) also appears (multiple times) on the web UI. All the After the problem occurs, I cannot use "Timeline" as well.However, after a clean start of
aw-server-rust, I can still view the "timeline" without error of a time range that includes the days that caused the error at "Activity".My sqlite database is like 200MB, and it obviously contains my privacy, so I am unable to share it.
The text was updated successfully, but these errors were encountered: