Guard repeated graph-memory LLM failures - #43
Merged
adoresever merged 1 commit intoAug 1, 2026
Conversation
adoresever
approved these changes
Aug 1, 2026
adoresever
left a comment
Owner
There was a problem hiding this comment.
核心方案已采纳并合并:连续配置类错误的冷却保护是必要的。合并时把触发范围收窄为持久配置错误(401/403/404),避免 400/422 等请求级错误错误地停用 LLM,并补充了测试。感谢贡献。
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.
Summary
LlmFailureGuardfor permanent graph-memory LLM API failuresWhy
This turns a runaway failure mode into a bounded cooldown when the configured memory LLM is misconfigured or unavailable.
Split from #39.
Verification
npm testnpx tsc --noEmit