Open kno10 opened 4 months ago
When reloading too often during testing, this can cause a rate limit on binderhub. The error is only logged to the console, the status is still "launching".
It would be best if a status "launch failed" could be presented to the user:
Error [server][abcabcabc] Binder: failed to build - https://mybinder.org/build/gh/executablebooks/thebe-binder-base/HEAD - Rate limit exceeded. Try again in 3600 seconds.
Uncaught (in promise) Rate limit exceeded. Try again in 3600 seconds.
Clicking then "run" just yields the (silent) error "Attempting to execute on a cell without an attached kernel", but no attempt to start a new kernel.
Use thebe with binder. Reload the page several times.
No response
Describe the bug
When reloading too often during testing, this can cause a rate limit on binderhub. The error is only logged to the console, the status is still "launching".
It would be best if a status "launch failed" could be presented to the user:
Error [server][abcabcabc] Binder: failed to build - https://mybinder.org/build/gh/executablebooks/thebe-binder-base/HEAD - Rate limit exceeded. Try again in 3600 seconds.
Uncaught (in promise) Rate limit exceeded. Try again in 3600 seconds.
Clicking then "run" just yields the (silent) error "Attempting to execute on a cell without an attached kernel", but no attempt to start a new kernel.
Reproduce the bug
Use thebe with binder. Reload the page several times.
List your environment
No response