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
while syncing bsc via llama's node the following error occurs eth_getLogs range is too large, max is 10k blocks
Expected behavior
the error should be handled by the surrounding code. it would be great to parse out the error that is seen from this situation, but that seems too custom a move given that an rpc provider could change their error messages or metadata and ponder would have to adjust. covering 90% of use cases with a block range constraint could be a simpler fix. #1361
Steps to reproduce
run the project, after filling out the example env for .env.local
Version
[email protected]
Current behavior
while syncing bsc via llama's node the following error occurs
eth_getLogs range is too large, max is 10k blocks
Expected behavior
the error should be handled by the surrounding code. it would be great to parse out the error that is seen from this situation, but that seems too custom a move given that an rpc provider could change their error messages or metadata and ponder would have to adjust. covering 90% of use cases with a block range constraint could be a simpler fix. #1361
Steps to reproduce
run the project, after filling out the example env for .env.local
for rpc 56, use a llama rpc
Link to repository
https://github.com/gibsfinance/bridge-indexer
Anything else?
The text was updated successfully, but these errors were encountered: