-
Notifications
You must be signed in to change notification settings - Fork 0
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
Students not vanishing from the queue #174
Comments
Please keep in mind that we do not have a formal operational responsibility for QWait. I can personally not afford to put time into fixing these bugs. It's good to keep track of bugs, but there is no guarantee that they will be fixed within two weeks, or in the foreseeable future. |
I know! I was just pointing out the problems that we found, and that they
On Fri, 26 Sep 2014, David Flemström wrote:
|
+1; this is a recurring problem at the DD1368 labs. I will see if I can put together a pull request when I have the time. Maybe during the upcoming summer. |
+1; this is still a problem and seems to occur if you close your browser without leaving the queue. |
At the ADK lab session this week we used Qwait and had the problem that many students were not removed from the queue, which meant that all seven teaching assistants went to a computer to look for a student that weren't there. I think that the reason for this is that you are logged out from the server too soon, and when you are not logged in you may not remove yourself from the queue - the button to remove yourself is not active. The solution for this is to make it possible to use that button even if you are not logged in anymore. Or by not logging out anyone who is in the queue.
Also there were students trying to change their information (about their location for example) without success. Problably of the same reason - that they were not logged in anymore.
Also there were students who left the location empty, which is not good when you have several rooms for the lab.
The next big lab session in ADK is in two weeks, and I don't think we can afford to use QWait if these problems are still there.
The text was updated successfully, but these errors were encountered: