We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
currently we call out to ExternalAddrs on the nat manager way too often, we need to find a way to cache this intelligently.
@jbenet this might also explain why some nodes still have sooooo many addresses that they advertise.
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
I think time based caching will be a good quick short term solution. This is a fairly major issue, since it crashes our most used command.
Indeed
issue has been addressed, but the symptoms still occur for other reasons. closing.
No branches or pull requests
currently we call out to ExternalAddrs on the nat manager way too often, we need to find a way to cache this intelligently.
@jbenet this might also explain why some nodes still have sooooo many addresses that they advertise.
The text was updated successfully, but these errors were encountered: