chore: bump sei-config to v0.0.25 - #501
Merged
Merged
Conversation
Keeps the controller's pin in sync with seictl v0.0.70. v0.0.25 sets the seed profile's max_incoming_connection_attempts to 32 and carries the giga_executor baseDefaults change. No behavior change here: the controller consumes sei-config for mode strings, port constants and the ConfigIntent shape, never DefaultForMode — config rendering happens in the seictl sidecar (sidecar/tasks/config_apply.go). Planner, task and platform tests pass unchanged. Ledger: bdchatham-designs designs/seed-node-mode/xreview/sei-config-v0.0.25-rollout.md Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
PR SummaryLow Risk Overview This keeps the controller aligned with the newer sei-config release (seed Reviewed by Cursor Bugbot for commit 9a794b8. Bugbot is set up for automated code reviews on this repo. Configure here. |
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
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.
Keeps the controller's
sei-configpin in sync with seictl v0.0.70 (sei-protocol/seictl#242).No behavior change. The controller consumes sei-config for mode strings, port constants and the
ConfigIntentshape — neverDefaultForMode. Config rendering happens in the seictl sidecar (sidecar/tasks/config_apply.go), which is why the sidecar image is the delivery vehicle for v0.0.25's seed cap and not this image.Diff is the pin plus two
go.sumlines.go mod verifyclean,go vetclean, and the sei-config-consuming packages (internal/planner,internal/task,internal/platform) pass unchanged.Context
v0.0.25 sets the seed profile's
max_incoming_connection_attemptsto 32 (concurrent connections per source IP) and carries sei-config#42'sGigaExecutorbaseDefaults change.Worth knowing for anyone reading the rollout:
TaskConfigApplyruns on the init path only — update plans carry onlyp2pConfigPatch(planner.go:787-796; convention stated atplanner.go:68-69and:821). So a sidecar bump does not re-render config on running nodes. The seeds take the new default by being deleted and recreated.Full T3 xreview:
designs/seed-node-mode/xreview/sei-config-v0.0.25-rollout.mdinbdchatham-designs(#130).🤖 Generated with Claude Code