fix(serverless): functions timeout #276
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About
Fix functions timeout not working properly in serverless (but working fine in runtime).
This is because serverless uses a
LocalPoolHandleto always execute an isolate on the same thread while allowing to have multiple threads to run a pool of isolate. Usingtokio::task::spawn, the timeout future is spawned on the same thread as the isolate, and will be blocked when the isolate blocks (e.g long script parsing, infinite loops...).The solution is to use a
tokio::task::spawn_blockingto spawn the timeout future on another thread where we can block.