DanConwayDev f25eea8cc3 fix: fetch full git history instead of shallow clones ...

Previously, purgatory sync was using '--depth=1' when fetching OIDs from
remote servers. This created shallow clones with only 1-2 commits instead
of the complete git history.

The fix removes the '--depth=1' flag, allowing git to fetch the complete
commit history chain when fetching specific commit OIDs. This is the
correct behavior for GRASP - users cloning from our relay should get the
full repository history.

Changes:
- Remove '--depth=1' from git fetch command in RealSyncContext::fetch_oids
- Update comment to clarify that full history is fetched

Impact:
- Production repositories will now contain full git history
- Users cloning from the relay will get complete commit chains
- No more 'shallow' files in git repositories
- May be slightly slower due to fetching more data, but correctness is prioritized

Testing:
- All 564 tests pass (276 unit + 288 integration)
- No regressions in existing functionality

Fixes issue documented in work/active-issues/shallow-git-fetch.md

2026-01-12 10:57:50 +00:00

..

context.rs

fix: fetch full git history instead of shallow clones

2026-01-12 10:57:50 +00:00

functions.rs

Add naughty list for git remotes with persistent SSL/DNS errors

2026-01-10 02:15:22 +00:00

loop.rs

Add naughty list for git remotes with persistent SSL/DNS errors

2026-01-10 02:15:22 +00:00

mod.rs

Add RealSyncContext implementation for production purgatory sync

2026-01-07 14:01:47 +00:00

queue.rs

Add SyncQueueEntry with exponential backoff for purgatory sync

2026-01-07 11:21:26 +00:00

throttle.rs

Add naughty list for git remotes with persistent SSL/DNS errors

2026-01-10 02:15:22 +00:00