Skip to content

fix: 修复首次监听绑定失败后的自动恢复与资源回滚 - #73

Merged
CSJ608 merged 1 commit into
mainfrom
codex/fix-63-listener-retry
Sep 8, 2026
Merged

CSJ608 merged 1 commit into
mainfrom
codex/fix-63-listener-retry

Conversation

@CSJ608

@CSJ608 CSJ608 commented Sep 8, 2026

Copy link
Copy Markdown
Owner

首次 Bind 失败会留下未监听的 _server,端口释放后仍无法恢复。本次改为在局部 Socket 完成配置、Bind/Listen 后发布,失败立即释放;监听器发布与停机释放互斥,迟到初始化不能在停机后重新占用端口。保留接受循环代次、单客户端关闭语义与公共 API。

新增 7 项回归:日志同步点确认绑定失败后释放端口,验证自动接入、双向消息与第二客户端拒绝;取消/Dispose 各覆盖失败后的停机、已发布 Socket 关闭/端口释放、排队初始化与停机竞争。同步事件和锁控制顺序,不用固定睡眠判定恢复。CHANGELOG Unreleased 已更新。

验证:

Closes #63

@CSJ608
CSJ608 merged commit d738104 into main Sep 8, 2026
5 checks passed
@CSJ608
CSJ608 deleted the codex/fix-63-listener-retry branch September 8, 2026 08:07
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.

bug: [P1] 首次 Bind 失败后残留无效监听 Socket,端口释放后仍无法自动恢复

1 participant