-
Notifications
You must be signed in to change notification settings - Fork 83
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
maint: Update Husky to handle invalid content type errors #1019
Conversation
e584949
to
f1a5e0e
Compare
} | ||
} else { | ||
// Since we have an invalid content type for an OTLP HTTP response we choose to use to text/plain | ||
if err := husky.WriteOtlpHttpFailureResponse(w, req, otlpErr); err != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the error here always a content type error?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, API key missing or invalid errors are also possible to come through here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
right, the description says it will use plain for content type errors, but this changes the behaviour for all errors?
## Which problem is this PR solving? - Releasing #1019 ## Short description of the changes - update CHANGELOG and RELEASE_NOTES - no documentation updates - no dependency license changes
Which problem is this PR solving?
Updates Husky to v0.25.1 which includes fixes handling invalid content types for OTLP requests.
See the following PR for changes:
NOTE: This PR is based on an unreleased version of husky. We'll wait for husky to be released before merging this fix.
Short description of the changes