You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It then kicks out the relayer process and restarts it.
I assume this means one of the chains doesnt have a specific endpoint, but it doesnt tell me which chain which makes debugging harder.
Additionally RLY should be more able to ignore certain fatal errors for one specific chain and just run the others in the config instead of completely erroring out.
The text was updated successfully, but these errors were encountered:
Thanks for opening the issue. I think this is a very valid request, i'll see if we can't get someone to dig into this more and provide some clearer logs with regards to the problematic query. I'll also try to replicate this at some point and see why Nomic has this issue as well.
With regards to the relayer process being killed and not just the processor for the specific chain, i agree. I started to take a stab at this somewhat recently but got pulled over to other tasks. I think it mostly just needs some testing. Ideally this is something we can get included in the next big release
Our larger config (over 40 chains) keeps running into this error:
It then kicks out the relayer process and restarts it.
I assume this means one of the chains doesnt have a specific endpoint, but it doesnt tell me which chain which makes debugging harder.
Additionally RLY should be more able to ignore certain fatal errors for one specific chain and just run the others in the config instead of completely erroring out.
The text was updated successfully, but these errors were encountered: