You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running into an issue where if you close a worker while it is trying to get data, it does not gracefully stop the listen command. This causes the lock to be stuck for an entire queue. There shouuld be an option to manually unlock, or set a timeout for the lock in these situations. Realistically the lock should be short lived, so anything over maybe a minute is most likley due to an issue or stuck lock.
The text was updated successfully, but these errors were encountered:
That is weird, because we use with statement. Which should correctly remove the lock on raised exception or worker exit. I need to look into it more closely.
Yeah, I saw the same thing and was surprised. I will also note I see tasks that were mid run get marked as failed with error "Keyboardinterupt", so may only be issue when a process gets hard killed.
Running into an issue where if you close a worker while it is trying to get data, it does not gracefully stop the listen command. This causes the lock to be stuck for an entire queue. There shouuld be an option to manually unlock, or set a timeout for the lock in these situations. Realistically the lock should be short lived, so anything over maybe a minute is most likley due to an issue or stuck lock.
The text was updated successfully, but these errors were encountered: