fleet/cmd/osv-processor
Konstantin Sykulev 2b4b96bf50
fixing shallow clone boundary error (#42662)
Related issue: Resolves https://github.com/fleetdm/fleet/issues/41571

It appears that there is some sort of error with shallow cloning.
```
Run echo "=== Generating OSV Artifacts for Ubuntu ===" 
=== Generating OSV Artifacts for Ubuntu ===
=== OSV Repository Sync ===

Repository exists, updating with rolling window...
fatal: error processing shallow info: 4
Error: Process completed with exit code 128.
```

Since we are only keeping a limited history of the repository via cache
before re-clone, fall back to doing a regular `git pull`. This avoids
the complicated shallow cloning / Git having to reconcile the
overlapping but different shallow boundaries, which can cause "error
processing shallow info: 4".


## Testing

- [x] QA'd all new/changed functionality manually


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Refactor**
* Modified repository synchronization to use full fetches instead of
rolling-window shallow fetches.
  * Updated sync status messaging for clarity.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-03-30 11:45:14 -05:00
..
main.go OSV artifact generation for use in vulnerabilities repository (#42203) 2026-03-25 13:02:26 -05:00
main_test.go OSV artifact generation for use in vulnerabilities repository (#42203) 2026-03-25 13:02:26 -05:00
sync-and-detect-changes.sh fixing shallow clone boundary error (#42662) 2026-03-30 11:45:14 -05:00
transforms.go OSV artifact generation for use in vulnerabilities repository (#42203) 2026-03-25 13:02:26 -05:00
transforms_test.go OSV artifact generation for use in vulnerabilities repository (#42203) 2026-03-25 13:02:26 -05:00