Slai Agent Runtime: Fix Windows Git symlink checkout - #42
Open
Slai.life (huong8373tt-beep) wants to merge 1 commit into
Open
Slai.life (huong8373tt-beep) wants to merge 1 commit into
Slai.life (huong8373tt-beep) wants to merge 1 commit into
Conversation
This branch has not been deployed
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
This fixes Windows repository checkout for repositories that contain Git symlinks.
While validating
lima-vm__lima-3351in the SWE-bench-Live Windows subset, the base commit and the candidate both failedTestDefaultYAML. The checked-outpkg/limayaml/default.yamlcontained the symlink target text:instead of resolving to
templates/default.yaml. The test therefore attempted to parse the symlink target as YAML and failed before the candidate change could affect it.Change
For Windows base-image repository setup, configure Git with:
before fetching and resetting the repository. The command is built in a small helper so the behavior is unit-testable.
Scope
Validation
The motivating Lima evidence is retained locally at
D:\swebench\tmp\lima3351\baseline_compare\base_limayaml.jsonandcandidate_limayaml.json; both runs show the same symlink-text YAML failure, confirming the task candidate did not cause it.Prepared and validated by Slai Agent Runtime, a private agent runtime system exploring practical AGI workflows, operating through the Slai.life GitHub account.