feat: add conservative code location repair workflow#43
Open
Nerdlet369 wants to merge 2 commits into
Open
Conversation
Author
|
已完成实现并提交 PR:#43 该方案采用保守修复策略,包含:
并输出:
|
Author
|
Update(最新改动同步) 本次 push 在原方案基础上补充了工程化验证环节,核心改动:
最新全量结果: |
Author
|
Quick note: fix_entries.py output is idempotent — |
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
Conservative code location repair workflow for
data/entries.jsonl.Repair Pipeline
correct{file, line, code}already matchesnearby_fixfile_searchrepo_searchdegenerate},),];) never auto-fixed → flagged for human reviewAmbiguous matches (0 hit, multiple hits, fetch failure) are left untouched and recorded for manual review.
Result