Skip to content
Novus Examples
patch1.2 KB

Git Patch - LF Line Endings Throughout

The LF half of the patch twin pair, identical in text content to the CRLF fixture. Diff the two downloads to get a change that is invisible in every renderer and fatal to a byte comparison.

Preview — first 42 linespatch
From 3fc638edf2bb468573d0b7af84e26eff9fc766ec Mon Sep 17 00:00:00 2001
From: Ada Fernsby <ada.fernsby@example.invalid>
Date: Thu, 12 Mar 2026 08:15:00 +0000
Subject: [PATCH] feat(ledger): treat a zero delta as a no-op

Identical bytes to the LF twin apart from the line terminators.
---
 internal/ledger/apply.go | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/internal/ledger/apply.go b/internal/ledger/apply.go
index 95f499d..ce501c6 100644
--- a/internal/ledger/apply.go
+++ b/internal/ledger/apply.go
@@ -1,14 +1,21 @@
 package ledger
 
-import "errors"
+import (
+	"errors"
+	"fmt"
+)
 
 // ErrShortBalance is returned when a posting would drive the balance negative.
 var ErrShortBalance = errors.New("ledger: insufficient balance")
 
 // Apply posts one delta against the running balance and returns the new total.
+// A zero delta is a no-op and never reports an error.
 func Apply(balance, delta int64) (int64, error) {
+	if delta == 0 {
+		return balance, nil
+	}
 	if balance+delta < 0 {
-		return balance, ErrShortBalance
+		return balance, fmt.Errorf("%w: balance %d, requested %d", ErrShortBalance, balance, delta)
 	}
 	return balance + delta, nil
 }
-- 
2.43.0

Specifications

Seed
20260807
Line Endings
LF
Files
1
Twin
CRLF
Encoding
UTF-8
Signature Line
-- (trailing space then LF)

Testing contract

Expected to pass
Scenario
Byte-compare the two patch twins and then compare them after line-ending normalisation.
Expected result
The raw files differ in length by exactly the number of lines; after normalisation they are identical.

What is a .patch file?

A .patch file is a unified diff packaged for transmission, most often as produced by `git format-patch`. Beyond the diff itself it carries an email-style header with the author, date, and commit subject, a commit message body, per-file `diff --git` headers recording renames and mode changes, and hunk headers of the form `@@ -old,count +new,count @@`. Applying it reconstructs a specific change against a specific before-state.

How to use this file

Use an example .patch file to test patch application, code-review renderers, and diff parsers — exercising renames, mode changes, binary hunks, added and deleted files, and the `\ No newline at end of file` marker that naive parsers silently drop.

How to use this file for testing

“Git Patch - LF Line Endings Throughout” is a deterministic Novus Examples fixture for Encoding detection, Visual diff / regression, Editor testing. UTF-8, UTF-8-BOM, UTF-16, and Latin-1 files with documented encodings and line endings for testing charset detection.

Documented properties for this file: seed 20260807 · UTF-8 · LF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Diff and patch fixtures name their target paths and the exact edge case they exercise — rename, mode change, binary hunk, CRLF↔LF, or missing trailing newline. Apply or render them against the documented before-state; every author, path, and hash is fictional.

Generated by generation/version_control.py. Free for any use, no attribution required — license.