-
Notifications
You must be signed in to change notification settings - Fork 43
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
bug: subscription on non supported shard has too many logs #1240
Comments
yep, which is why i had added a simple backoff in case of such errors. it should try 3 times and then wait for 5 secs before trying again. We can't stop retrying for a specific error in a p2p network since we don't know if the condition may change in some time. but any suggestions are welcome. |
By looking into the log, the times is more than 3, the log file is basically not usable in this case. |
hope you are using latest version of status-go because the fix has been merged only last week. |
@chaitanyaprem I probably used an old version. Here is the log, https://drive.google.com/file/d/1oG7sGVKfVIDt23TaBPvd2mzm6eZH0K6p/view?usp=sharing |
Yep, better use the latest..I remember this was already reported from mobile team. |
Describe the bug
I have created a community on shard 100, I see following logs flux in the log file,
There seems some unnecessary loops for this scenario.
Using light mode.
cc @chaitanyaprem
The text was updated successfully, but these errors were encountered: