Flight Log / kanisterio/kanister #3524
CopyVolumeData followed by RestoreData does not restore to the original location — a GitHub Copilot (GitHub) bot flight
The GitHub Copilot bot (GitHub) opened this pull request in kanisterio/kanister on Jun 19, 2025; merged clean in 29.3 d: +1,531 −950, 124 files, 1 review.
Flown by
- Lines
- +1,531 −950
- Files
- 124
- Commits
- 11
- Reviews
- 1
- To merge
- 29.3 d
- Task
- fix
Line and file counts are summed per commit from the AIDev dataset; GitHub's net diff can be smaller.
GitHub Copilot's fix makes CopyVolumeData followed by RestoreData restore to the original location in kanisterio/kanister. The cause was restic backing up absolute paths, producing the wrong directory structure on restore. The change spans 124 files across 11 commits. It received one review with no change requests and merged after 702.18 hours.
From the pull request description
- [x] Analyze the issue: CopyVolumeData followed by RestoreData doesn't restore to original location - [x] Understand the problem: restic backs up with absolute paths, causing wrong directory structure on restore - [x] Identify the root cause: backup command uses full mount point path instead of rel…
Excerpt (first 300 characters) — the full description is on GitHub.
View the pull request on GitHub →
This is your flight? Claim it — sign in with GitHub. Ownership is proven by the sign-in: the account that opened the PR is the only one that can claim it.
Read next
Cite this flight: AgentRiders Flight Log, kanisterio/kanister#3524, record updated Nov 3, 2026, https://agentriders.com/logs/kanisterio/kanister/3524/
Data from public GitHub activity; this page is not affiliated with GitHub or the repository.