-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Latest watchers do not pick up withdrawal finalization #1041
Comments
@smartcontracts ah found the issue and fixed it here: #1121 Our integration tests no longer hand and all pass with this mini change directly implemented in our node_modules. |
@smartcontracts it seems like the fix proposed in #1121 allows some L2>L1 withdrawal's get picked up, but it still times out on some situations. |
Confirmed that I was able to reproduce locally
Withdrawal succeeds on first few tries, but then |
Looks like batch submitter is failing with logs
|
@K-Ho @ajsantander this is a pretty old issue. Is this still relevant? |
Closing this out, I assume this is fixed |
This happens when we upgrade
@eth-optimism/watcher
to@eth-optimism/core-utils
as can be seen in this PR https://github.com/Synthetixio/synthetix/pull/1321/filesThe result is that the watcher "hangs" when detecting withdrawal finalization, even though it seems to pick up deposit finalization. This can be seen as a timeout of 10m in the previously mentioned CI run https://app.circleci.com/pipelines/github/Synthetixio/synthetix/7427/workflows/fcf5e4f3-527f-4fe8-8e78-4f5ce376ec9d/jobs/69921
To reproduce locally, check out the Synthetix repo at the PR above, start the ops tool at the specified commit, then run:
npx hardhat test:integration:dual --compile --deploy
This is how we setup the watcher: https://github.com/Synthetixio/synthetix/pull/1321/files#diff-0ec74ac23703db180e935294b0032c83811c218e87dacfdf89637dca21d4e352L70-L80
And how we use it: https://github.com/Synthetixio/synthetix/blob/develop/test/integration/utils/watchers.js
The text was updated successfully, but these errors were encountered: