-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug(alloy
+ anvil
): data did not match any variant of untagged enum SerializableTransactionType
#9324
Comments
This transaction has @grandizzy @mattsse unsure if we need to take any action here? eg we could add |
That did the job! Thank you. Maybe flag a warning that this was deprecated? Although, IMO it's unlikely a lot of people use this feature... Maybe its OK just as a breaking change. |
I'm OK with taking no action here, since the breaking change is already introduced and an workaround exists. |
I tend to agree, this ticket can serve as a reference for anyone that does happen to run into the issue. The new |
Re-opening, this will be resolved as part of #9280 (comment) It looks like there have been other breaking changes in Alloy that should be handled gracefully, including this one. |
alloy
+ anvil
): data did not match any variant of untagged enum SerializableTransactionType
Component
Anvil
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (31c24b0 2024-11-14T00:20:56.222819000Z)
What command(s) is the bug in?
anvil --load-state
Operating System
macOS (Apple Silicon)
Describe the bug
Running:
Gives me:
However, this command worked on a previously working edition of foundry & anvil.
I was able to revert to an older version where I did not get such an error with the following command:
Here is the block that was erroring:
Where
line 1 column 11125
was pointing to the spot I have markedError here
.This
state.json
was created on an older version of anvil using--dump-state
originally.The text was updated successfully, but these errors were encountered: