We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug in current situation Sentry issue: https://sentry.io/organizations/registries/issues/2341978216/events/155b37f253264d2889bbcb1fbc3fdf65/
Sentry reports a simple error: GET /users/@me returned a 404 (not found) -- which is obvious because that's an incorrect URL (missing Auth Api Url).
But I don't think it's that simple, since this call seems to succeed for most users.
In this scenario, it appears that the root cause is that the Auth Api Url is empty.
See also Sentry issue: https://sentry.io/organizations/registries/issues/2098686855/events/e7b8b9d91f30415f8704ec14c1cb8a80/
(I think both Sentry issues were generated in response to the same events.)
Link bug to the User Story
Impact of this bug Describe the impact, i.e. what the impact is, and number of users impacted.
Chance of Occurring (high/medium/low/very low)
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Steps to Reproduce Steps to reproduce the behavior:
Actual/ observed behavior/ results
Expected behavior A clear and concise description of what you expected to happen. Use the gherking language.
Screenshots/ Visual Reference/ Source If applicable, add screenshots to help explain your problem. You an use screengrab.
The text was updated successfully, but these errors were encountered:
closed due to old sentry error. can reopen if it keeps happening
Sorry, something went wrong.
No branches or pull requests
Describe the bug in current situation
Sentry issue: https://sentry.io/organizations/registries/issues/2341978216/events/155b37f253264d2889bbcb1fbc3fdf65/
Sentry reports a simple error: GET /users/@me returned a 404 (not found) -- which is obvious because that's an incorrect URL (missing Auth Api Url).
But I don't think it's that simple, since this call seems to succeed for most users.
In this scenario, it appears that the root cause is that the Auth Api Url is empty.
See also Sentry issue: https://sentry.io/organizations/registries/issues/2098686855/events/e7b8b9d91f30415f8704ec14c1cb8a80/
(I think both Sentry issues were generated in response to the same events.)
Link bug to the User Story
Impact of this bug
Describe the impact, i.e. what the impact is, and number of users impacted.
Chance of Occurring (high/medium/low/very low)
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Steps to Reproduce
Steps to reproduce the behavior:
Actual/ observed behavior/ results
Expected behavior
A clear and concise description of what you expected to happen. Use the gherking language.
Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.
The text was updated successfully, but these errors were encountered: