-
Notifications
You must be signed in to change notification settings - Fork 64
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
Prevent catastrophic failures from resulting in no results #723
Comments
@chrispyles This is causing us a lot of issues, appears to stem from this change 461ec0f. Anyway to do a hotfix/5.1.4? |
Relevant pr #728 |
I'm currently working on a fix for this but not sure how long it will take. If it's a super important issue I can put this into a bugfix release (i.e. v5.1.4) ahead of v5.2.0. As noted in my comment in #728, that PR does not actually fix the underlying issue. |
@chrispyles We have around 1000 students using this and running into this issue (example error below). It still emits the ZIP file that we need, so it's not blocking, but there is confusion over it.
|
@ctnelson1997 I'm not sure how much a fix for this will help for your issue. The fix I'm proposing here doesn't fix the fact that an I'm not sure why the error you provided is getting thrown -- it looks like something unrelated to this issue and would require more debugging. If you just want to silence the error, you could disable the submission zip validation in |
Hi @chrispyles this appears to be a platform compatibility issue with the use of NamedTemporaryFile. For anyone not on a Unix machine (e.g. Windows, like mine) the NamedTemporaryFile cannot be opened again. Thus, results cannot be written, which I believe is what's causing the file to be empty, leading to the |
It's possible for a catastrophic failure to occur when Otter runs the student notebook s.t. the executed notebook produces no results pickle file, e.g.
Otter should handle this case gracefully by returning a score of 0 and alerting the student/instructor to the failure instead of completely erroring out.
The text was updated successfully, but these errors were encountered: