fix: refresh Knowhere JWTs during long QStash workflows - #164
Merged
Conversation
Expired Dashboard snapshots were reported as workflow auth failures even when Knowhere parsing later succeeded. Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
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
1 participant
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.
Summary
Authentication requiredso hour-plus parses are not marked failed after the snapshotted 1h JWT expires.Depends on Dashboard Ontos-AI/knowhere-dashboard#98 — deploy that first, or refresh calls 404 and workflows still fail the same way.
Test plan
pnpm testJWT refresh + reconcile/parsed-sync continuation testsSource reconciliation workflow failed: Authentication required)KNOWHERE_API_KEY/sk_credentials are not sent to refreshMade with Cursor