Repository navigation
onggi diff --ranges: changed byte ranges per file (#46) - #48
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
aicomp #129 asks the engine to switch a resident NPU build to another build of the same model by uploading only the changed parts. For that, the engine needs the changed byte ranges per file, and
onggi diffreported only totals (#46).Changes
Store.DifftakesDiffOptions{Ranges}. With it,FileDiff.Changedlists the changed runs as[offset, length]; every other byte is at the same offset in the paired base file.onggi diff --ranges [--json].Verification
changed_runs, and cover exactlysize - same; the bytes before the first range equal the base. Without the option,changedis absent..rbln):The first 70 KB and the last 218 MB differ; the 15.0 GB between them is identical at the same offsets. Formats are not parsed (ADR-0009); these are byte positions only.
Compatibility and limits
Store.Diffgained a parameter (Go API). The CLI output is unchanged without--ranges.Related Issue
Closes #46
🤖 Generated with Claude Code