-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
improve check block old detection #10733
improve check block old detection #10733
Conversation
I see that you haven't updated any CHANGELOG files. Would it make sense to do so? |
Running downstream job at https://github.com/smartcontractkit/operator-ui/actions/runs/6251807839 |
Running downstream job at https://github.com/smartcontractkit/operator-ui/actions/runs/6252525163 |
Running downstream job at https://github.com/smartcontractkit/operator-ui/actions/runs/6252531059 |
Running downstream job at https://github.com/smartcontractkit/operator-ui/actions/runs/6252617110 |
Running downstream job at https://github.com/smartcontractkit/operator-ui/actions/runs/6252653392 |
saw on matic, some payloads were stuck in retry loop as they were getting
missing trie node
erroradding that string to error check. Don't fully like the approach of handling error strings which got us here, open to better solutions
We're not fully relying on just latest-checkBlock > checkBlockTooOldRange because the range can differ from chains, and the existing 128 range was too small for arbitrum, causing lots of payloads to error out early