-
Notifications
You must be signed in to change notification settings - Fork 18
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
Failure trace is hard to process #63
Comments
In https://github.com/nexB/fetchcode/blob/ab65b2e645c889887227ea49eb3332d885fd0a54/src/fetchcode/package.py#L41 the code is problematic because this is trying to get the JSON before checking if the request was successful (e.g. a 200 HTTP answer)... otherwise it does not make sense to get JSON until we know the request succeeded:
|
closed by #73 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This failure is cryptic and it does not tell anything that can help me fix it...
In contrast if I update the code this way:
I now have a clean and clear failure trace that is actionable:
We should test and ensure we have informative traces in all our functions
The text was updated successfully, but these errors were encountered: