-
Notifications
You must be signed in to change notification settings - Fork 301
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
Programing exercise
: Student does not see the results from the latest submission in the overview
#9086
Comments
The changes from #8741 may have fixed the issue. I cannot reproduce the error message in the log. We will keep it open and check if the problem occurs in the next semester again. |
Hi @BaumiCoder, it appears that one of our courses encounters the issue as well. So it may not be fully fixed. We are currently using Artemis 7.6.5 |
Emphasis on the additional context:
We use PostgreSQL, @dfuchss what DB are you using? To make it potentially easier to reproduce and determine if the problem only occurs with PostgreSQL. The likely cause in any case is that some query does not ensure the correct order but uses them as-is as received from the database. Log output probably from an unrelated problem that occurred at a similar time. Getting the latest result and the ScoreScheduleService should be independent. |
We are using MySQL 🤔 |
But I think for us it's related to the locking of an exercise. |
Reproduction steps:
|
I think I can trace it back to the This is filled by the On the server side, it is likely that the problem originates somewhere in |
Describe the bug
The overview of a Programming exercise sometimes does not show the results from the latest submission. Instead it shows the result of a previous submission.
To Reproduce
Expected behavior
The overview on the left-hand side always shows the results for the latest submission.
Screenshots
The overview on the left-hand side shows here a warning symbol, but the latest submission has no warning. But as you can see all previous submissions have a warning. It looks like the
Which version of Artemis are you seeing the problem on?
7.4.3 (and also older version)
What browsers are you seeing the problem on?
Other (specify in "Additional context")
Additional context
The visual impact of the bug, which the screenshot shows, appears on our productive Artemis server and was noticed by one student. The reproduction in a test environment was not successful yet, but an error in the log seems to indicate what is the problem behind it.
An
Query did not return a unique result
error occurs which indicates that there is not deterministic which result is selected here. The problem appears with PostgreSQL, maybe this problem is also related to some difference between MySQL and PostgreSQL.Relevant log output
full log entry with stracktrace
The text was updated successfully, but these errors were encountered: