feat(worker): add SILVERBACK_FORK_MODE handler execution context #157
+46
−8
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.
What I did
This PR adds a settings mode to silverback to trigger every single registered handler (through the default registration interface) using a fork context (e.g.
with ape.networks.fork(): ...
). This potentially unblocks theBacktestRunner
andsilverback test
by allowing all tests to execute within a fork context off of historical stateHow I did it
depends: ApeWorX/ape#2349
How to verify it
Checklist
- [ ] New test cases have been added and are passing