Skip to content

Slai Agent Runtime: Fix Windows Git symlink checkout - #42

Open
Slai.life (huong8373tt-beep) wants to merge 1 commit into
microsoft:mainfrom
huong8373tt-beep:slai-fix-windows-git-symlinks
Open

Slai.life (huong8373tt-beep) wants to merge 1 commit into
microsoft:mainfrom
huong8373tt-beep:slai-fix-windows-git-symlinks

Conversation

@huong8373tt-beep

Copy link
Copy Markdown

Summary

This fixes Windows repository checkout for repositories that contain Git symlinks.

While validating lima-vm__lima-3351 in the SWE-bench-Live Windows subset, the base commit and the candidate both failed TestDefaultYAML. The checked-out pkg/limayaml/default.yaml contained the symlink target text:

../../templates/default.yaml

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:

git config --global core.symlinks true

before fetching and resetting the repository. The command is built in a small helper so the behavior is unit-testable.

Scope

  • Windows checkout path only.
  • No evaluator or task-source changes.
  • Existing non-Windows checkout behavior is unchanged.

Validation

python -m py_compile launch/core/platforms/windows.py tests/runtime_test.py
python -m pytest -q tests/runtime_test.py -k windows_repo_clone_enables_git_symlinks
# 1 passed, 6 deselected

The motivating Lima evidence is retained locally at D:\swebench\tmp\lima3351\baseline_compare\base_limayaml.json and candidate_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.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant