script: fix db/cmp update header indentation#160
Merged
Conversation
db/cmp prefixes context lines in its diff output with two spaces. When
support for -scripttest.update was added to db/cmp in commit e2a88e6931c
("script: support -scripttest.update in db/cmp"), it accidentally reused
that diff-prefixed header for the replacement content when writing the
new golden file. This was causing updated table files to gain two
leading spaces before the first header column.
Fix this by keeping the diff prefix only in the diff output and write
the replacement header without indentation.
Fixes: 1e2a88e ("script: support -scripttest.update in db/cmp")
Reported-by: Jussi Maki <jussi.maki@isovalent.com>
Signed-off-by: Tobias Klauser <tobias@cilium.io>
db/cmp update header indentation
|
joamaki
approved these changes
Jun 9, 2026
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.
db/cmpprefixes context lines in its diff output with two spaces. When support for-scripttest.updatewas added todb/cmpin commit e2a88e6931c ("script: support -scripttest.update in db/cmp"), it accidentally reused that diff-prefixed header for the replacement content when writing the new golden file. This was causing updated table files to gain two leading spaces before the first header column.Fix this by keeping the diff prefix only in the diff output and write the replacement header without indentation.
Fixes: 1e2a88e ("script: support -scripttest.update in db/cmp")
Reported-by: @joamaki