You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the student's submission calls os._exit(0), the final feedback in A+ is completely empty. I assume that the python-grader-utils process shuts down and is not able to produce any output in the end.
I got the remotegrader working with our recent updates to graderutils.
When using the remotegrader, os._exit(0) results in an EOFError when the rpyc connection is lost, but it does not shut down the main process.
os._exit() could probably be overridden in the student process so that it raises an exception stating that the command should not be used. Is this too hacky?
I think overriding could also work in the current non-rpyc graderutils.
If the student's submission calls
os._exit(0)
, the final feedback in A+ is completely empty. I assume that the python-grader-utils process shuts down and is not able to produce any output in the end.Is the remote grader prototype able to fix this problem? If the grader main process and the submission process are separated, then the student can not shut down the main process.
https://github.com/apluslms/python-grader-utils/tree/remotegrader
The text was updated successfully, but these errors were encountered: