Repository navigation
fix(agent): 修复 MEMMY-592 输出位置与完整交付核验(v1.2.6) #677
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
yxyi123
wants to merge
2
commits into
MemTensor:v1.2.6
from
yxyi123:fix/memmy-592-output-location-v126
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
交付失败后清除了清单,用户继续任务时会漏检缺失文件。模型声明生成 report.pdf 和 data.xlsx,实际只生成 PDF,两轮修复后仍缺 Excel。本轮会正确提示“尚未确认交付”,但用户接着说“继续完成刚才的两个文件”时,如果模型直接回复全部完成,缺失的 Excel 就不会再被拦截。补充探针通过真实 processDirect 连续两轮复现了这个结果。
原因是这里在没有运行中的生成任务、且停止原因不是 deliveryPending 时就调用 retire(),交付核验失败的 toolError 也满足条件。retire() 同时清空文件清单和 pendingOutputDelivery 标记,下一轮创建的是没有任何交付义务的新状态。
建议将“本轮停止”和“文件任务结束”分开:核验失败、模型错误或预算耗尽后保留未完成清单,同一任务继续时仍核验全部文件;成功交付或明确取消/开始新任务时再清理。普通用户入口和子任务结果入口共用的发布逻辑需要一起调整,并补上“缺第二文件→修复耗尽→用户继续→仍缺文件不得完成”的跨轮回归,同时验证成功与取消后不会污染新任务。