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
{{ message }}
This repository has been archived by the owner on Jun 27, 2023. It is now read-only.
I noticed an issue when submitting answers for challenges on certain browsers the site freezes and becomes unresponsive, forcing the browser to terminate.
This happens in:
Chrome 78.0.3904.108 on Windows 10
MS Edge 42.17134.1098.0
Tried fixing it but got lost in the recursion, seems like in _tryProofOfWork the params variable is never defined under Chrome, the execution never reaches testbits and gets stuck a loop. Also debugged with Burp the api call is not issued before the freeze.
The text was updated successfully, but these errors were encountered:
Okay after a few hours of debugging I managed to find a workaround. If you set PROOF_OF_WORK_BITS to zero in the config.py file it basically turns off the proofofwork token feature and the browser doesn't get stuck in a loop. You do have to restart the server and hit a few Crtl-F5s in the browser after setting it because the js gets cached.
So add this to config.py: PROOF_OF_WORK_BITS = 0
I noticed an issue when submitting answers for challenges on certain browsers the site freezes and becomes unresponsive, forcing the browser to terminate.
This happens in:
Chrome 78.0.3904.108 on Windows 10
MS Edge 42.17134.1098.0
Tried fixing it but got lost in the recursion, seems like in _tryProofOfWork the params variable is never defined under Chrome, the execution never reaches testbits and gets stuck a loop. Also debugged with Burp the api call is not issued before the freeze.
The text was updated successfully, but these errors were encountered: