-
Notifications
You must be signed in to change notification settings - Fork 11.7k
[pkg-alt] Fix simtests #23755
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
[pkg-alt] Fix simtests #23755
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
LGTM
| let chain_id = read_api.get_chain_identifier().await?; | ||
|
|
||
| // For upgrade, we want to force the root package to have `0x0` as its address | ||
| build_config.root_as_zero = 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.
shouldn't this also be set in publish_command function?
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.
discussed offline: we shouldn't be doing it for publish. We should protect from accidental dual publishes.
If someone wants to republish, they first need to remove the entry from Published file.
Description
Fix the first issue with simtest failures
Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.