-
Notifications
You must be signed in to change notification settings - Fork 60
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
[FEAT]: should 304 conditional requests be logged as errors? #725
Comments
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with |
there is no error level logging in this module, it is either log level debug or info |
I am specifically looking at this line:
This is what we've overridden in our own Octokit scripts to log this as info and not error if |
The root of this issue is not in this module but rather in request.js/src/fetch-wrapper.ts Lines 124 to 131 in 1ffa99b
We throw an error specifically if the status is a 304 All this plugin does is catch errors from requests and logs them with the error level |
OK, fair. We'll just keep patching in our world. Thanks! |
Describe the need
Not sure if this is a request to "change the default behavior" or "allow some magical flags to customize"...
We make use of conditional requests a lot. We've had to patch the standard Octokit opinionated plugin choices with a version where we treat a
304
error.status
as informational instead of an error - our server logs were full of all the conditional requests that "successfully" returned 304s.Not sure if this is something that's come up before, but would love to know how common it is that others do not want to see endless log spew such as this...
Just a comment.
SDK Version
N/A
API Version
N/A
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: