feat: default DM relays with race condition fix#194
Merged
Conversation
The previous implementation checked keyRepo.getDmRelays() synchronously after EOSE, but kind 10050 events were still being processed async by EventRouter. This caused false negatives that overwrote existing DM relay lists with defaults. Now reactively waits on dmRelaysFlow and also queries write relays (outbox) as a second source before concluding the user has no DM relays.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
wss://auth.nostr1.com) for users who have no DM relays configured, and broadcast the relay list to indexersdmRelaysFlowand queries write relays (outbox) as a second source before concluding the user has noneTest plan
wss://auth.nostr1.comis applied as defaultDM relays arrived during waitvsApplied default DM relaysto confirm correct detection