fix: retry embedding on next poll when Workers AI call fails#31
Merged
liplus-lin-lay merged 1 commit intomainfrom Apr 5, 2026
Merged
fix: retry embedding on next poll when Workers AI call fails#31liplus-lin-lay merged 1 commit intomainfrom
liplus-lin-lay merged 1 commit intomainfrom
Conversation
エンベディング生成失敗時に bodyHash が保存されてしまい、次回ポーリングで needsEmbedding=false となって永久にリトライされないバグを修正。 - エンベディング失敗時は bodyHash を空にして保存し、次回ポーリングで再試行 - IssueStore に POST /reset-hashes エンドポイントを追加(既存stuck レコードの再同期用) - ポーリングログに failed カウントを追加 Refs #30 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
github-rag-mcp | 15e3b13 | Apr 05 2026, 12:51 PM |
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
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.
Refs #30
エンベディング生成失敗時に bodyHash が保存されてしまい、次回ポーリングで再試行されないバグを修正。
bodyHash を空で保存することで次回ポーリングでリトライさせ、既存 stuck レコード用に reset-hashes エンドポイントを追加。