Skip to content

fix(pchronicle): fix distributed S3 manifest writes - #129

Merged
reiase merged 4 commits into
mainfrom
feat/pchronicle-s3-conditional-write
Sep 14, 2026
Merged

reiase merged 4 commits into
mainfrom
feat/pchronicle-s3-conditional-write

Conversation

@lizhicui

@lizhicui lizhicui commented Sep 9, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • retry conditional S3 writes once with an unquoted ETag when the provider rejects the quoted form with 412 ConditionNotMatch
  • remove the single-writer object-store manifest mode and its CLI/configuration plumbing so Gateway capture remains safe for distributed replicas
  • include per-source automatic Storyline projection failures in readiness errors

Validation

  • targeted pChronicle tests passed before deployment (68 passed)
  • deployed extended OpenAI tools workload passed with all five tool scenarios executed and no missing tools
  • restart recovery passed: 6 canonical events and 6 Storyline turns remained readable with identical response hashes
  • two-replica workload passed after re-establishing the test port-forward; no ConditionNotMatch, PreconditionFailed, or Storyline startup errors observed
  • deployment restored to 1 replica

Preserve main's storage exports, retry layer, conflict logging, and CLI contracts while retaining the PR's conditional ETag compatibility and manifest mode removal.
@lizhicui
lizhicui force-pushed the feat/pchronicle-s3-conditional-write branch from aa1e720 to bd6c432 Compare September 14, 2026 07:20
@reiase
reiase merged commit 1f9c094 into main Sep 14, 2026
26 of 27 checks passed
@reiase
reiase deleted the feat/pchronicle-s3-conditional-write branch September 14, 2026 08:17
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.

2 participants