User experience - failed code run doesn't stop running
saul-data opened this issue · 0 comments
saul-data commented
To reproduce:
- Stop any workers
- Go to code editor, run a python file
- Wait for retries to finish
- Error message comes back but doesn't stop the runner. There are no error websockets, only an error graphql.
- User needs to exit code editor and come back. Clicking stop fails to stop the run.
Fix options:
- Check if an error websockets needs to be sent from backend rather than front end change.
- Stop button to stop the run.
- Possible to simulate in cypress tests where worker needs to be stopped? Maybe an environment with no workers?