-
Notifications
You must be signed in to change notification settings - Fork 132
Fix flaky follows on sign up, mobile C-2718 #6219
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -742,7 +742,6 @@ function* watchConfigureMetaMask() { | |
| function* watchFollowArtists() { | ||
| while ( | ||
| yield all([ | ||
| take(signOnActions.SIGN_UP_SUCCEEDED), | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We don't need to watch |
||
| take(accountActions.fetchAccountSucceeded.type), | ||
| take(signOnActions.FOLLOW_ARTISTS) | ||
| ]) | ||
|
|
||
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
interesting, so simply removing this allows the fetch to continue, that right?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah this was redundant because we call fetchAccountAsync after putting
SIGN_UP_SUCCEEDEDhttps://github.com/AudiusProject/audius-protocol/blob/main/packages/web/src/common/store/pages/signon/sagas.js#L499-L501.For some reason web always executed the
fetchAccountAsyncfirst before theSIGN_UP_SUCCEEDEDwatchers (which includes the follow artists fn), while mobile did not always do the same.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are def other ways to fix this though... We could remove the watch for
accountActions.fetchAccountSucceeded.typehere as well and just callsignOnActions.FOLLOW_ARTISTSat the end of the sign up saga afterfetchAccountAsynchttps://github.com/AudiusProject/audius-protocol/blob/main/packages/web/src/common/store/pages/signon/sagas.js#L499-L501. Or we could add a watcher forsignOnActions.signUpSucceededWithId(userId)(called here) that sets the user id in the account store so that we don't have to wait to fetch the full account before doing the follows.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fine for now cause with the new sign up flow pretty much all of this will go away
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooh gotcha I thought all the sagas were staying the same and just the Ui was changing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True but some of these sagas are not needed. For instance this fetch artists saga can just be an Audius-query thing inside the relevant components