Repository navigation
Feature/v0.1/wasm instances config limits - #4
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Limits: Basic Fuel metering for CPU protection.
This PR introduces improved resource-limiting mechanisms for Wasm execution, enabling fine-grained CPU control and more resilient runtime behavior.
Custom fuel limits for Wasm instances
Previously, users could only choose preset levels (Low, Medium, High).
This PR adds support for specifying an exact custom fuel value, offering precise CPU metering and better protection against abusive workloads.
Full timeout management
Adds complete handling of execution timeouts within a Wasm instance, ensuring tasks cannot exceed their allocated runtime.
Retry policy management
Introduces robust retry handling when a Wasm instance crashes.
max_retries is now fully configurable and defaults to 0 (no retries).
Enhanced CI/CD pipeline
The CI now runs:
clippyfor lintingrustfmtfor formatting