Conversation
Three "republished elsewhere" notifications arrived in one session and
the versions they named went BACKWARDS:
1 1788102406-8d4f live: 1788102406-8d4f my own publish
2 1788113439-87c9 live: 1788115237-56b7 mine, newer
3 1788114931-eac9 live: 1788115237-56b7 mine, unchanged
The third named a version older than the second. The stream replays
superseded versions rather than announcing new ones, so the check needs
no judgement -- it needs an ordering comparison:
if the named id is older than the one the fetch returns, it cannot
be a publish you have not seen; stop there.
The version prefix is a unix timestamp, so 1788114931 < 1788115237
settles it without opening the file. One integer comparison against the
ninety thousand tokens the first of the three cost.
The body diff is still there and is still right; it is simply only
reached when the ids say something moved. On its first use after being
written, this section turned a full re-read into two commands.
Refs #2966
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
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
1 participant
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.
Three "republished elsewhere, your copy is stale" notifications arrived in one session, and the versions they named went backwards:
1788102406-8d4f1788102406-8d4f— my own publish1788113439-87c91788115237-56b7— mine, newer1788114931-eac91788115237-56b7— mine, unchangedThe third named a version older than the second. The stream is replaying superseded versions rather than announcing new ones, so the check does not need judgement — it needs an ordering comparison:
The version prefix is a unix timestamp, so
1788114931 < 1788115237settles it without opening the file — one integer comparison against the ninety thousand tokens the first of these three cost.The body diff from the original section is still right; it is simply only reached when the ids say something actually moved.
On its first use after being written, §410 turned a full re-read into two commands — the fetch, and
diff, which printedidentical. All four iteration-41 markers were present in the live page and nothing needed republishing.Refs #2966
🤖 Generated with Claude Code