-
Notifications
You must be signed in to change notification settings - Fork 146
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
Prioritize evaluations with finished grading for review #1668
Conversation
As discussed, a small test would be nice :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for contributing!
We already order the evaluations by vote_end_date
and num_unreviewed_textanswers
in find_unreviewed_evaluations
. For consistency, we should do all sorting at the same place, and I think inside that method is a good place. I'd suggest removing the order_by
call on the queryset and calling sorted
once in python.
While you're editing that method: I think the final .all()
call is a no-op, you could remove that if you want.
Edit: If you feel the method name could be improved, I'd agree 100%, so go for it if you want :)
You can find the |
@PonderKoKo do you want to continue working on this or should we take over? |
Hey @janno42 , sorry, but I've been feeling pretty stressed in the last couple of weeks. I would try to finish it up, but I can't really say how soon that will be. If it's fine to take a little longer, I will, but feel free to take over otherwise. |
@PonderKoKo that is totally fine with us, just wanted to check in on you. Our next update is due in at least two weeks or so, it would of course be great if it would be closed until then - not a hard requirement though. Please just make sure to tell us, if you want to drop working on this issue at some point :) |
hey @PonderKoKo, how do you do? we'd like to go on with this issue. don't worry, if you don't have the time or interest to do it yourself, we can help you or take it over, just let us know. |
Hey, I couldn't figure out why the following happens in the test I'm writing:
And
|
The 403 forbidden was caused by Another issue then is that Then, everything works, and the test gets to the print statement. You can find a working version here: richardebeling@a992679 In case you didn't know: You don't have to wait for the tests if you use
Does this solve your problem? |
I hope I did this correctly now. |
This reverts commit d88c2ec.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good to me. I think we can shrink the test a little and then I'm fine with merging :)
Co-authored-by: Richard Ebeling <dev@richardebeling.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✔️ Meets requirements
✔️ UI functionality checked
Closes #1663