-
Notifications
You must be signed in to change notification settings - Fork 31
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
fix(auth): clean up auth exception handling #1104
fix(auth): clean up auth exception handling #1104
Conversation
…Auth fail) responses
Wait a minute, looks like I broke something just before pushing. Whoops. Checking. |
Or not... ? |
https://github.com/cryostatio/cryostat/actions/runs/3200604186/jobs/5227713966
and the server-side logs:
So it looks like the test container came up in JDP, but Cryostat wasn't able to connect to it afterward. Not sure why that happened. And this class of failure should probably be a |
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.
Looks good to me! Solved the front-end issue when testing. I think maybe a test expected status code needs changing following this updates ?
Error: Failures:
Error: WrongServiceListeningOnPortIT.testConnectionFailsAsExpected:112
Expected: <500>
but: was <502>
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.
Looks good to me as well, I will use the AbstractAuthenticatedRequestHandler connection exception handling in my issue :-)
Okay, I think this is actually settled this time. |
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.
Looks great to me! Thanks for fixing this :D
Fixes #1102