-
Notifications
You must be signed in to change notification settings - Fork 179
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
Add DefaultFVMOptions to verification builder #5439
Add DefaultFVMOptions to verification builder #5439
Conversation
... so that it also affects VNs. We should clean this up to avoid similar mistakes in the future. See issue: #5249
@@ -240,7 +240,6 @@ func DefaultFVMOptions(chainID flow.ChainID, cadenceTracing bool, extensiveTraci | |||
AttachmentsEnabled: chainID != flow.Mainnet, | |||
}, | |||
)), | |||
fvm.WithEVMEnabled(true), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at the option above, does that mean that attachments are currently broken on VNs too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, good catch.... yes.
let me address that.
Should this target |
I assume we are going to merge the two together soon rigth? Since we are deploying from here I thought I would just put it here. @j1010001 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Let's also fix this on master, but we can already get this in on this feature branch to unblock a new image and update of the previewnet deployment
master PR #5440 |
f6d50be
into
feature/stable-cadence
... so that VNs have the same context as ENs.
We should clean this up to avoid similar mistakes in the future. See issue: #5249