Skip to content

Read the second server for the count this paragraph asserted - #362

Merged
iderex merged 1 commit into
masterfrom
docs/the-second-row-of-that-count-was-written-not-read
Sep 5, 2026
Merged

iderex merged 1 commit into
masterfrom
docs/the-second-row-of-that-count-was-written-not-read

Conversation

@iderex

@iderex iderex commented Sep 5, 2026

Copy link
Copy Markdown
Collaborator

Refs #9

What was wrong

The paragraph recording that IItemRepository.DeleteItem is not declared on the
12.0 line pasted its reading as two rows of one command:

git show origin/master:docs/supported-servers.md | sed -n '122,124p'
    git grep -c "DeleteItem" v10.11.11 v12.0-rc4 -- MediaBrowser.Controller/Persistence/IItemRepository.cs
    v10.11.11:...:1
    v12.0-rc4:...:0

That command produces one row. git grep -c prints nothing at all for a file it
counted no match in, so a row ending in :0 is not output it can emit:

git grep -c "DeleteItem" v10.11.11 v12.0-rc4 -- MediaBrowser.Controller/Persistence/IItemRepository.cs
v10.11.11:MediaBrowser.Controller/Persistence/IItemRepository.cs:1

Run at G:/Github/jellyfin. So the second row was written rather than read, and
it stands in the paragraph whose whole subject is a claim about a second server
made without asking it.

What it reads now

One revision at a time, where a zero is a number the command does print:

git show v10.11.11:MediaBrowser.Controller/Persistence/IItemRepository.cs | grep -c DeleteItem
1
git show v12.0-rc4:MediaBrowser.Controller/Persistence/IItemRepository.cs | grep -c DeleteItem
0

The claim does not move and neither does the argument built on it. What moves is
that the reading behind it reproduces.

How it was found, and what else that pass covered

Every reading in these documents taken from a Jellyfin checkout was re-run
against the checkout it was taken from, block by block. The rest reproduce. This
was the only block asserting a line no run produces; the differences elsewhere
are the dedent this file applies to every pasted body, which is consistent across
the page and is not a claim.

What holds it

Nothing, and that is unchanged rather than newly conceded. The suite has no
server to ask, so no leg here re-derives a reading of a Jellyfin checkout. This
page says so in its own last section and SupportedServersTests says so in its
own remarks, and both already covered this block. No leg is added and none is
claimed.

VSTEST_CONNECTION_TIMEOUT=300 DOTNET_CLI_UI_LANGUAGE=en dotnet test Jellyfin.Plugin.MetadataSync.sln --nologo
Failed: 0, Passed: 1696

per target, over both server lines, before the change and after it.

What this does not move

No condition of #9 changes. This is a repair to a reading the page rests on.

Reading

No second reader looked at this. The commands above are the evidence in place of
one.

The paragraph recording that `IItemRepository.DeleteItem` is not declared on
the 12.0 line pasted the reading as two rows of one `git grep -c`, and the
second row is a line that command cannot emit: the verb prints nothing at
all for a file it counted no match in, so a row ending in `:0` is not
output. That row was written rather than read, inside the paragraph whose
whole subject is a claim about a second server made without asking it.

The reading is replaced with one `git show | grep -c` per revision, where a
zero is a number the command does print, and both reproduce at
`G:/Github/jellyfin`. The claim and the argument built on it do not move.

Found by re-running every server-source reading in the documents against the
checkout they were taken from. The others reproduce; this one was the only
block asserting a line no run produces.

No leg is added and none is claimed: the suite has no server to ask, which
this page's last section and the suite's own remarks already say.

Signed-off-by: Nils Lehnen <30603423+iderex@users.noreply.github.com>
@iderex iderex added the documentation Improvements or additions to documentation label Sep 5, 2026
@iderex iderex self-assigned this Sep 5, 2026
@iderex
iderex merged commit 74f5d62 into master Sep 5, 2026
14 of 15 checks passed
@iderex
iderex deleted the docs/the-second-row-of-that-count-was-written-not-read branch September 5, 2026 07:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant