Skip to content
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

Caching issue with annotations in feedback player #637

Open
fosterfarrell9 opened this issue May 3, 2024 · 3 comments
Open

Caching issue with annotations in feedback player #637

fosterfarrell9 opened this issue May 3, 2024 · 3 comments
Assignees
Labels

Comments

@fosterfarrell9
Copy link
Collaborator

fosterfarrell9 commented May 3, 2024

In production, I experienced the following issue with annotations: A student had made an annotation in a video, and that annotation was shared with me. I noticed the anotation when I opened the feedback player. Then I went through the other videos of my lecture and was puzzled to see the exact same annotation in all of them, always at the same time (when it did not make any contextual sense). It turned out that the annotation vanished in the feedback player when I did a page "shift reload". After that I opened the feedback player for the video that actually contained the annotation and noticed that it had been gone. A "shift reload" of the page made it reappear. Apparently, there are some caching issues here. I can reproduce the behaviour in development.

@fosterfarrell9
Copy link
Collaborator Author

I played around locally a bit in order to get a feeling for what is going on. It seems that the problem appears when you make use of the browser's Back-button (while seems not to appear when you separately open different feedback players in different tabs). In the case where annotations are displayed that belong to a video from before in the browsing history, no update_annotations action is triggered. All of this leads me to suspect that turbolinks is what causes the problems.

@Splines Splines self-assigned this Aug 3, 2024
Splines added a commit that referenced this issue Aug 3, 2024
@Splines
Copy link
Member

Splines commented Aug 22, 2024

I made a fix for this that might have fixed it, but I'm not entirely sure. Could you check that this bug does not occur anymore in production?

@Splines Splines reopened this Aug 22, 2024
@fosterfarrell9
Copy link
Collaborator Author

Seems to work fine now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants