-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runner crash on first request on Linux (and maybe others) #42
Comments
Is this related to the issue reported by @SmiteDeluxe? |
Websockets seem to be supported out-of-the-box by |
|
This is the same issue
The
I chose |
Also see the
The potential future usage of was |
Closes #42 ### Summary of Changes - replaces flask with quart - rewrite some tests - added test against crashing - solution should be more scalable as it replaces wsgi with asgi --------- Co-authored-by: megalinter-bot <[email protected]>
## [0.5.0](v0.4.0...v0.5.0) (2024-01-26) ### Features * added json serializer that encodes tables and images ([#29](#29)) ([054cca4](054cca4)), closes [#20](#20) * Memoization ([#38](#38)) ([2a26b48](2a26b48)) * Replace flask with quart ([#43](#43)) ([5520b68](5520b68)), closes [#42](#42) * support placeholder queries that only request a subset of data ([#39](#39)) ([dae57dc](dae57dc)) * update to safe-ds 0.17.1 + server refactor ([#37](#37)) ([1bcad07](1bcad07)) ### Bug Fixes * allow multiple connections to work with the runner ([#31](#31)) ([64685a3](64685a3))
🎉 This issue has been resolved in version 0.5.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Describe the bug
The runner crashes on first request (usually program message)
To Reproduce
Expected behavior
The runner executes the program
Screenshots (optional)
No response
Additional Context (optional)
I would propose to replace the (legacy) flask stack with a quart (successor in a way of flask) stack that does not require monkey patching python internals. This has the added benefit to allow async python functions and in turn being possibly more efficient.
Furthermore, a migration to the socket.io protocol is still possible although not as easy as changing the dependency in flask.
The text was updated successfully, but these errors were encountered: