-
Notifications
You must be signed in to change notification settings - Fork 9
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
Dupe student user remixes #1128
Comments
@sra405 I've added all I know here, but if you could flesh it out with any further info, that would be great |
Branch issues/1128-Dupe_student_user_remixes created! |
So far: managed to fix displaying the student names if there are duplicate students, but still unsure why multiple remixes are being created |
Looks like the get request for the remix when the project is revisited isn't happening, it sends a get request for the original project instead. Then when the user clicks save, it successfully remixes the original project again, but does a get for the first remix and returns that. e.g. https://telemetry.betterstack.com/team/54242/tail?s=314882&q=lyric-dent-math with remixes at Could it be that there is a race condition between loading the user into state and requesting the project? If the project is being requested before the user is properly loaded, it may well assume that the user is not logged in and therefore load the original project rather than requesting the user's remix. |
This is an issue in staging that @MFarringtonRPF observed, which led to a second remix being erroneously created for a user, and one of them not displaying user details on the Student Work page. There is a chance that old data might have a part in it.
The ids of Mel's projects where the issue was observed:
This query shows possible further scenarios where this has been seen in prod:
Example problem records:
Logs:
First remix: https://logs.betterstack.com/team/54242/tail?s=314882&q=recap-slept-enter
Second remix: https://logs.betterstack.com/team/54242/tail?s=314882&q=perky-iron-half
The text was updated successfully, but these errors were encountered: