Commit e4c9b89
fix(restore): properly propagate compaction errors during restore
Fix variable scoping bug where compaction errors were being lost.
The error from c.Compact() was captured in an if-statement scope,
but the outer `err` variable (nil on NewCompactor success) was
passed to CloseWithError, causing compaction failures to result
in misleading EOF errors instead of the actual error.
Note: The root cause of issue #858 (GCS restore EOF errors) was
already fixed in PR #807 (commit 5cb6fd6) which translates size=0
to length=-1 for GCS range reads. This PR fixes a secondary bug
discovered during investigation.
Related: #807
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>1 parent fc6a020 commit e4c9b89
1 file changed
+2
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
483 | 483 | | |
484 | 484 | | |
485 | 485 | | |
486 | | - | |
| 486 | + | |
| 487 | + | |
487 | 488 | | |
488 | 489 | | |
489 | 490 | | |
| |||
0 commit comments