fix(runtime): Fix runtime timeouts #5236
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
The handling for epoch-based timeouts wasn't quite right. Using `set_epoch_deadline(1)` meant the timeout would be hit on the next epoch, which could be anywhere between `0` and `timeout` seconds away. `set_epoch_deadline(2)` will make that between `timeout` and `2*timeout` seconds away.
leoyvens
force-pushed
the
leo/fix-timeouts-for-new-wasmtime
branch
from
656da4f to
09bd64a
Compare
mangas
approved these changes
Feb 23, 2024
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.
The handling for epoch-based timeouts wasn't quite right. Using
set_epoch_deadline(1)meant the timeout would be hit on the next epoch, which could be anywhere between0andtimeoutseconds away.set_epoch_deadline(2)will make that betweentimeoutand2*timeoutseconds away.