Since it's possible that there will be other bug we haven't found yet, detect when sbws is stalling.
Also print backtrace so that operators can open tickets with the backtrace and help to find the bug.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
I think we should make 36 value into some sort of constant because it isn't clear what is that value but also it is repeated twice.
I had to read the loop above to get that it is every 5 seconds and thus 36 is for 3 minutes. Either adding a clearer comment linking the two or making it a constant and comment there.
The other thing is that, don't you want to exit after the bug is detected or it will recover from the mistake?
I think we should make 36 value into some sort of constant because it isn't clear what is that value but also it is repeated twice.
I had to read the loop above to get that it is every 5 seconds and thus 36 is for 3 minutes. Either adding a clearer comment linking the two or making it a constant and comment there.
Added a constant.
The other thing is that, don't you want to exit after the bug is detected or it will recover from the mistake?
No, the error doesn't recover. I changed the code so that it exits unless the debugging level is log (more verbose) so that it continues instanciating a Python Debugger (for developers to debug the error).