Draft
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.
What changed
This adds a small
util/testutilhelper for Anvil-backed integration tests that need Filecoin precompile addresses to exist.0xfe...Filecoin precompile addressesSetupFVMPrecompilesandRegisterActorIDhelpers for testsRESOLVE_ADDRESSbehavior and the minimal supported actor-call happy pathsWhy
Some integration tests want contracts to stop reverting on empty Filecoin precompile addresses when running against an Anvil fork.
This is intended as an incremental test utility. It makes narrow precompile-backed test cases possible without implying that Anvil now emulates full Filecoin actor behavior.
Impact
Tests can now opt into lightweight precompile mocks when they need address resolution or minimal actor-call behavior.
This does not unblock the real DDO allocation flow end-to-end. In particular, it does not emulate the full
DataCapAPI.transfer/ VerifReg path used bycreateAllocationRequests.Validation
go test ./util/testutil -run 'TestIntegration_FVM' -count=1