Fix blank feed race condition on cold start#117
Merged
Conversation
EOSE and events travel on separate SharedFlows, so after EOSE arrives the kind 3 event may still be buffered waiting for the processing loop. Poll briefly to let it catch up before the caller reads the follow list, preventing a blank feed on ~10% of cold starts.
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
subscribeSelfData()returns before the follow list is processed, causing the feed setup to skip relay discovery and leave the user with a blank feedTest plan
subscribeSelfData: gotFollowList=trueon every attempt