GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||
GeezerVison is showing github.com — [python] Show why the server refused a credential. by blp · Pull Request #7858 · feldera/feldera Conversation
Member
Linked IssueRelated to #7048. This does not fix it. On a 401, the pipeline manager gives the reason in the In the two most recent reports in #7048 (runs 39514151001 and 41968241434), the token refresher log shows a refresh every 90 seconds with no misses. So the server refused tokens that had not expired. The client logs cannot show why. The 401 error message now has a Describe Manual Test PlanNew unit tests in Checklist
Breaking Changes?Mark if you think the answer is yes for any of these components:
Describe Incompatible ChangesNone. Only the text of 401 error messages changes.
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Contributor
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
12 tasks
mihaibudiu
approved these changes
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
On a 401, the pipeline manager gives the reason in the `error_description` of its `WWW-Authenticate` header, and the body is empty. The client error read only the body, so it said "credential rejected (invalid or expired token / API key)" for every refusal. In could not show why. The 401 error message now has a `Reason:` line with that description. Signed-off-by: Ben Pfaff <[email protected]>
blp
force-pushed
the
python-401-reason
branch
from
63dda0e to
4571416
Compare
|
There was an error while loading. Please reload this page.
|
It may help to also query /healthz in this case to find out more, I believe if the database is unreachable it could also result in a 401 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.