Skip to content

chore(fork): drop the streamed-write-timestamps patch - #178

Merged
fireboltdude1357 merged 1 commit into
patch/releasefrom
chore/drop-streamed-write-timestamps
Nov 3, 2026
Merged

fireboltdude1357 merged 1 commit into
patch/releasefrom
chore/drop-streamed-write-timestamps

Conversation

@fireboltdude1357

Copy link
Copy Markdown
Owner

The fork's nightly build fails at 21:31 on upstream 61c3794. Both the Linux and Mac legs stop on a parse error:

[PARSE_ERROR] Identifier `encodePayloadTimestamp` has already been declared

Upstream pingdotgg#25252 makes the same change as patch/streamed-write-timestamps. Message and turn-item writes now encode their timestamps directly instead of parsing the payload JSON back, and only the comment differs from the patch. It declares encodePayloadTimestamp in a different spot than the patch does, so git merges both copies without a conflict. The patch's own upstream PR, pingdotgg#25162, was closed.

The doc says to delete a patch's line once it merges upstream, so this removes streamed-write-timestamps from .github/fork-patches.txt. The branch stays.

On a scratch stack of upstream 61c3794 with the other 21 patches, the merge is clean and ProjectionStore.ts declares encodePayloadTimestamp once. pnpm install --no-frozen-lockfile, vp run typecheck (40 of 40) and vp test run on ProjectionStore.test.ts (53 tests, including upstream's new ones) pass.

Made by Claude Opus 5.5 in Claude Code.

🤖 Generated with Claude Code

Upstream pingdotgg#25252 made the same change, so merging the patch on top
declared encodePayloadTimestamp twice and broke both build legs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fireboltdude1357
fireboltdude1357 merged commit 95339ce into patch/release Nov 3, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant