feat: replayer result export, sei-config consolidation, and API cleanup#9
Merged
Conversation
- Add ResultExport to ReplayerSpec (not FullNodeSpec) enabling periodic block result export to S3 for replay workloads - Remove StartHeight from S3SnapshotSource; users specify an explicit S3 URI for a specific snapshot, height is auto-discovered from the key - Replace local wellKnownSnapshotChains map with seiconfig.KnownChain() - Replace local nodePorts/defaultSidecarPort with seiconfig port constants - Update sample manifest to pacific-1-shadow-replayer with inferred bucket - Bump sei-config to v0.0.7 and seictl to v0.0.15 - Remove stale conditions.go and pacific-1-replay.yaml Made-with: Cursor
bdchatham
force-pushed
the
feat/controller-quality-cleanup
branch
from
1340904 to
729ecab
Compare
bdchatham
commented
Mar 17, 2026
| defaultSnapshotUploadCron = "0 0 * * *" | ||
| defaultSnapshotInterval = int64(2000) | ||
|
|
||
| resultExportBucket = "sei-node-mvp" |
Collaborator
Author
There was a problem hiding this comment.
These will be updated to a real bucket once MVP is complete.
Made-with: Cursor
Made-with: Cursor
bdchatham
added a commit
that referenced
this pull request
May 19, 2026
…ind race) (#295) Live manual run on harbor surfaced this: `seictl nd watch --until=Ready` returns when SeiNode pods report Running (status.phase=Running, all plan tasks Complete) — but seid's Tendermint RPC server takes a few more seconds AFTER that to actually bind port 26657. The compute-target-height bash step's single-shot curl loses that race: curl: (7) Failed to connect to <snd>-internal.nightly.svc:26657 after 10 ms: Could not connect to server failed to parse latest_block_height from .../status Manual curl from a fresh pod 90s later returns HTTP 200 with height 286 — the chain IS up, just not at the instant `nd watch` returned. Wrap the curl in a 30-attempt retry loop with 3s sleep (90s window) and a 3s --connect-timeout. Matches the retry pattern resolve-proposal-id already uses (different step, same shape: chain-side query that needs to tolerate a brief warmup). Symptom chain on the live run: compute-target-height exits 1 → workflow-vars ConfigMap not created → downstream submit-upgrade-proposal seitask-runner pod stuck in CreateContainerConfigError because its envFrom configMapRef can't resolve. Single fix at the source resolves the whole cascade. Bug #9 in the major-upgrade-runs-end-to-end debugging chain. Same shape as several earlier ones: an assumption about timing/readiness that doesn't survive contact with the cluster.
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.
Summary
ResultExporttoReplayerSpec(exclusive to replayer, not full nodes) for periodic block result export to S3StartHeightfromS3SnapshotSource— users provide an explicit S3 URI for a specific snapshot; height is auto-discovered from the archive key namewellKnownSnapshotChainsmap withseiconfig.KnownChain()and local port constants withseiconfig.PortRPC,seiconfig.PortSidecar,seiconfig.NodePorts()running/completed/failed) instead of inferring fromCompletedAtpacific-1-shadow-replayer.yamlwith inferred S3 bucketsei-configto v0.0.7,seictlto v0.0.15conditions.goand oldpacific-1-replay.yamlsampleTest plan