chore: release v0.0.26 (configurable p2p accept-interval) - #48
Merged
Conversation
Carries #47, which threads `accept-interval` through both schema layers and the legacy mapping in each direction. That key is unreachable until it ships in a tagged version: sei-k8s-controller pins v0.0.25 (#501), which predates it, so a SeiNode setting accept_interval today has it silently dropped by the schema. The key matters because seid's inbound accept limiter defaults to 1/s and has never been reachable from config (sei-chain#3899). At that rate the kernel keeps completing handshakes into the listen backlog faster than the loop drains it, and arriving peers wait past handshake-timeout — from the dialer's side, a node that accepts TCP and then says nothing. Our three prod-cell seeds are in exactly that state. Releasing the key does not by itself change any node's behaviour: the value only takes effect on a seid build carrying sei-chain#3899, which is not yet merged and not yet in release/v6.6. This is the half of the delivery path that can move now, so the knob exists when that build lands rather than after. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
PR SummaryLow Risk Overview It tags work already on the branch (not changed in this diff), especially #47, which wires Runtime behavior does not change from this bump alone; the knob only matters once a seid build reads it (sei-chain#3899). This release unblocks operators and controllers to set the value in config ahead of that binary. Reviewed by Cursor Bugbot for commit de0a098. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Suggested version: Changes in (empty)
Automatically created GitHub ReleaseA draft GitHub Release has been created. |
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.
Cuts
v0.0.26, carrying #47 — the only commit sincev0.0.25.What ships
#47 threads
accept-intervalthrough both schema layers and the legacy mapping in each direction:config.go:216P2PConfig.AcceptInterval—toml:"accept_interval"legacy.go:78legacyP2P.AcceptInterval—toml:"accept-interval"legacy.go:433legacy.go:770defaults.go:7210msWhy cut it now
The key is unreachable until it ships in a tagged version. sei-k8s-controller pins
v0.0.25(#501), which predates #47, so a SeiNode settingaccept_intervaltoday has it silently dropped by the schema — no error, no warning.The key matters because seid's inbound accept limiter defaults to 1/s and has never been reachable from config (sei-protocol/sei-chain#3899). At that rate the kernel keeps completing three-way handshakes into the listen backlog faster than the accept loop drains it, so arriving peers wait past
handshake-timeoutand never finish. From the dialer's side that looks like a node which accepts TCP and then does nothing — which is the observed state of our threeprod-cell seeds.Behaviour
This release changes no node's behaviour on its own. The value only takes effect on a seid build carrying sei-chain#3899, which is not yet merged and not yet backported to
release/v6.6. This is the half of the delivery path that can move now, so the knob exists when that build lands rather than trailing it.Verification
go build ./...andgo test ./...clean on the branch. #47's own coverage inconfig_test.gocame with it.🤖 Generated with Claude Code