Use SimplePool
object in new nostr-tools for sending OTP codes to avoid relay connection closed errors
#20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
nostr-tools
package to give usSimplePool
.SimplePool
instead of the lower-levelRelay
object, as recommended by thenostr-tools
documentation.SimplePool
instance active on the app singleton object to avoid constant reconnection to relays.This is an attempt to fix damus-io/website#42, based on the investigation done there.
This is a tentative fix based off of an analysis of the logs, the report, and the code. The issue could not be definitively reproduced on a controlled setup, so this fix cannot be guaranteed to fix the issue in question, but has a good probability of fixing it.
Testing:
api: 38b3000
website: 322171d3f9a8c92568b822c54568021495d767e2
Setup: Local frontend and backend
Steps:
.env
to a separate file, then runnpm test
. Ensure tests pass.PASS