-
Notifications
You must be signed in to change notification settings - Fork 35
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
Build fails with latest @tenderly/hardhat-tenderly #32
Comments
fedgiac
added a commit
that referenced
this issue
May 4, 2023
Updates remaining outdated packages that are tightly coupled together and need to be updated in parallel. Note that Ethers has been updated to the latest minor version for v5, an upgrade to v6 requires many changes and will trigger a new major release of this project. Also note that I only updated Tenderly to v1.1 and froze it at that minor version. Using the latest version would require a few code changes, importing an extra package, increase the number of network request on _any_ invocation of `hardhat` and would annoyingly increase the amount of logs that are printed every time `hardhat` is called (the extra logs might be reduced but not configured away as the logging level is hardcoded in the plugin). Issue #32 is related. The changes to the proxy code appear to be caused by a change in behavior in `hardhat-deploy`, the new code should have the same effect (this is confirmed by our tests). I found a related issue [here](wighawag/hardhat-deploy#294) and the new behavior appears to be intended behavior. ### Test Plan Test a few commands and verify that everything works as usual, notably `yarn deploy` and `yarn bench:trace`.
This issue appears to have been fixed in #49. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Deleting
yarn.lock
, and the installing dependencies viayarn
, and finally attemptingyarn build:sol
fails with the following error:@tenderly/hardhat-tenderly had a release today, which coincides with this failure; there is a warning about an unsatisfied dependency, namely:
Oddly enough, downgrading to version
1.2.0
didn't work either (not sure why we didn't see that before), but that one also complains about unmettenderly@^0.0.1
, so that might be a clue.Finally, downgrading to
@tenderly/[email protected]
allows the build to run normally.The text was updated successfully, but these errors were encountered: