Closed critch closed 7 years ago
Thanks for debugging and reporting this @critch - this could perhaps explain some odd experiences with the video player.
In case you are able to work on the issue, we'll be there for any kind of assistance!
Otherwise we'll have someone look at it so it's fixed no later than 0.17.3 (since we better release the other one really soon).
I'm not really a Python person. I'm just enough of a tech and developer to get you the good info.
hi @critch .. May I ask if this is problem is specific to RHEL 7.2? I wanted to gather more information regarding to this issue.
I also tried to reproduce this on Mac from the steps you've given. Tried both Google Chrome and Firefox but the logs weren't giving me those kind of errors.
I happen to find a similar issue regarding with this current issue: API error after watching a video.
#4957 and 'User ID required for get_uuid' error at the end of video for non logged in users
#4073
@benjaoming mentioned that @jamalex fixed this before. Would you mind explaining what was causing this and how you fixed this issue? Thanks!
@mrpau-eugene sorry can't recall what I recalled back then. I've reopened #4957, try reproducing by having an admin user logged in?
Closing this as a duplicate then...
@benjaoming have tried those already but I was still unable to reproduce it. I saw someone fixed it by adding
!window.statusModel.get("is_admin)
in the close function. I'm just wondering why it's still occurring.
close: function() {
if (window.statusModel.get("is_logged_in") && !window.statusModel.get("is_admin") ) {
this.log_model.saveNow();
}
this.remove();
}
Maybe there were console errors appearing in the author's browser which might help..
This does appear to be a duplicate of the mentioned items.
@critch yes.. however the previous issues experienced this when logged in as administrator..
By the way, are there any errors in the console when you experienced this issue?
Summary
When viewing a video on a RHEL system with pip install KALite 0.17.1, a request is made to /api/videolog that results in a 500 error. This error when viewed from a tablet results in an overlay on the video that causes the video controls to no longer be accessible. There are actually many ways to trip the videolog call such as skipping around in the video. End result is always a 500 error.
System information
Traceback or relevant snippet from server.log
How to reproduce
Real-life consequences (anything community should be aware, for instance how it affects your deployment)
When this bug is tripped, it results in inaccessible video player controls on tablets. If triggered via skipping around, the video could be playing under the error message with no ability to stop the player.