Merge pull request #9297 from mr-raj12/fix/codespell-typos-1.4
Some checks failed
CI / lint (push) Has been cancelled
CodeQL / Analyze (push) Has been cancelled
Windows CI / msys2-ucrt64 (push) Has been cancelled
CI / asan_ubsan (push) Has been cancelled
CI / native_tests (push) Has been cancelled
CI / vm_tests (Haiku, false, haiku, r1beta5) (push) Has been cancelled
CI / vm_tests (NetBSD, false, netbsd, 10.1) (push) Has been cancelled
CI / vm_tests (OpenBSD, false, openbsd, 7.7) (push) Has been cancelled
CI / vm_tests (borg-freebsd-14-x86_64-gh, FreeBSD, true, freebsd, 14.3) (push) Has been cancelled

fix typos found by codespell (1.4-maint)
This commit is contained in:
TW 2026-02-12 20:50:48 +01:00 committed by GitHub
commit 7752addbee
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
4 changed files with 8 additions and 8 deletions

View file

@ -741,7 +741,7 @@ These are your options to protect against that:
How can I protect against theft, sabotage, lightning, fire, ...?
----------------------------------------------------------------
In general: if your only backup medium is nearby the backupped machine and
In general: if your only backup medium is nearby the backed-up machine and
always connected, you can easily get into trouble: they likely share the same
fate if something goes really wrong.
@ -794,7 +794,7 @@ Common issues
There can be many causes of this error. E.g. you have incorrectly specified the repository path.
You will also get this error if you try to access a repository that uses the argon2 key algorithm using an old version of borg.
We recommend upgrading to the latest stable version and trying again. We are sorry. We should have thought abount forward
We recommend upgrading to the latest stable version and trying again. We are sorry. We should have thought about forward
compatibility and implemented a more helpful error message.
Why am I seeing idle borg serve processes on the repo server?
@ -1413,7 +1413,7 @@ There are some caveats:
Why is my backup bigger than with attic?
----------------------------------------
Attic was rather unflexible when it comes to compression, it always
Attic was rather inflexible when it comes to compression, it always
compressed using zlib level 6 (no way to switch compression off or
adjust the level or algorithm).

View file

@ -818,7 +818,7 @@ bucket is reached.
This particular mode of operation is open addressing with linear probing.
When the hash table is filled to 75%, its size is grown. When it's
emptied to 25%, its size is shrinked. Operations on it have a variable
emptied to 25%, its size is shrunk. Operations on it have a variable
complexity between constant and linear with low factor, and memory overhead
varies between 33% and 300%.

View file

@ -1797,7 +1797,7 @@ class ArchiveChecker:
# if we kill the defect chunk here, subsequent actions within this "borg check"
# run will find missing chunks and replace them with all-zero replacement
# chunks and flag the files as "repaired".
# if another backup is done later and the missing chunks get backupped again,
# if another backup is done later and the missing chunks get backed up again,
# a "borg check" afterwards can heal all files where this chunk was missing.
logger.warning('Found defect chunks. They will be deleted now, so affected files can '
'get repaired now and maybe healed later.')

View file

@ -75,11 +75,11 @@ class XattrTestCase(BaseTestCase):
self.assert_equal(len(buffer), 128)
@pytest.mark.parametrize('lstring, splitted', (
@pytest.mark.parametrize('lstring, expected', (
(b'', []),
(b'\x00', [b'']),
(b'\x01a', [b'a']),
(b'\x01a\x02cd', [b'a', b'cd']),
))
def test_split_lstring(lstring, splitted):
assert split_lstring(lstring) == splitted
def test_split_lstring(lstring, expected):
assert split_lstring(lstring) == expected