Repository navigation
Jhrg/chaining msg update - #1440
Merged
Merged
Conversation
|
|
|
dh-opendap
approved these changes
Oct 13, 2026
dh-opendap
left a comment
dh-opendap
left a comment
Contributor
There was a problem hiding this comment.
Changes all seem reasonable and correct to me.
Collaborator
|
Looks OK. |
kyang2014
approved these changes
Oct 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Reference ticket: HYRAX-2284
We return the Service chaining error with CMR tells us it's a 401 and we return 'Service chaining' error messages for other HTTP-related errors that are not service chaining in the sense intended by this message. These message are (or were by me) intended to alert us to an issue in NGAP and should not apply to cases outside of NGAP.
Tasks