Skip to content
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

Lies to students about "staff being informed" if nuisance failure #1025

Open
inducer opened this issue Sep 18, 2023 · 0 comments
Open

Lies to students about "staff being informed" if nuisance failure #1025

inducer opened this issue Sep 18, 2023 · 0 comments

Comments

@inducer
Copy link
Owner

inducer commented Sep 18, 2023

Code questions have some ad-hoc logic about classifying container launch issues as "nuisance failures":

relate/course/page/code.py

Lines 370 to 398 in 35cd621

def is_nuisance_failure(result):
if result["result"] != "uncaught_error":
return False
if "traceback" in result:
if "BadStatusLine" in result["traceback"]:
# Occasionally, we fail to send a POST to the container, even after
# the inital ping GET succeeded, for (for now) mysterious reasons.
# Just try again.
return True
if "bind: address already in use" in result["traceback"]:
# https://github.com/docker/docker/issues/8714
return True
if ("requests.packages.urllib3.exceptions.NewConnectionError"
in result["traceback"]):
return True
if "http.client.RemoteDisconnected" in result["traceback"]:
return True
if "[Errno 113] No route to host" in result["traceback"]:
return True
return False

If every container launch retry fails because of a nuisance issue, the current error message claims that "staff is being informed", but that is not true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant