Repository navigation
GITHUB-4: 修复旁路摘要不完整时直接失败的问题 - #135
Merged
Merged
Conversation
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.
旁路问答在准备上下文时,摘要固定使用 2048 tokens;遇到空正文、输出截断或工具调用就直接失败,并统一显示“旁路摘要未完整生成”。用户手动重试会重复相同路径。本地测试库没有现场历史,尚不能确认报告中的具体失败类型或频率。
空正文、截断及摘要过长时,现在使用原材料自动重试一次,将输出预算提高到 8192 tokens,并要求更精简的摘要。分块提前为恢复预留空间,失败或半段摘要不写入缓存;重试仍计入原有 12 次调用上限及 120 秒超时。最终错误区分具体失败原因。部分适配器仍透传推理强度,提高预算用于容纳这类端点可能的推理消耗,是否充分解决现场问题需要独立审查。
验证:
go test -race ./sidequestion -count=1通过,覆盖空正文、仅思考、两种截断、摘要过长、多分块、窗口预算、取消、调用上限、用量及缓存完整性。go build ./cmd/artex通过(验证时产物写入临时工作目录)。TestSideTaskArchiveVersions(含三个子测试)及TestSideTaskContextModelUnavailableIsDistinct失败;使用起始提交的摘要源码与测试通过 Go overlay 复跑,失败项及通过数一致,属于已有基线问题。请独立验证问题机制及修复正确性,特别关注推理预算、额外调用开销、小窗口分块和缓存一致性。
Closes GITHUB-4