initFromManifest: a failed adopt of the socket listener should be non-fatal #90

Open
opened 2026-09-05 19:09:44 +00:00 by a73x · 0 comments
a73x commented 2026-09-05 19:09:44 +00:00 (Migrated from git.a73x.sh)

server.zig initFromManifest does 'try serve.adopt(d.listener_fd, sock_path)' for the unix socket, so an adopt that fails (path unlinked in the sub-millisecond window around the exec) aborts the upgrade and rolls back. The agent socket's adopt on the same path is non-fatal. With Server.watchSockPath in place, adopting with a lost path and letting the watch re-bind on its first tick is the consistent shape. Review finding 2026-09-05, judged not blocking for the socket-lifecycle branch.


Migrated from git-collab issue f25709a32c738cbd459aa7ee24b0869d9ce16329.

Original author: a73x dev@a73x.sh.

server.zig initFromManifest does 'try serve.adopt(d.listener_fd, sock_path)' for the unix socket, so an adopt that fails (path unlinked in the sub-millisecond window around the exec) aborts the upgrade and rolls back. The agent socket's adopt on the same path is non-fatal. With Server.watchSockPath in place, adopting with a lost path and letting the watch re-bind on its first tick is the consistent shape. Review finding 2026-09-05, judged not blocking for the socket-lifecycle branch. --- Migrated from git-collab issue `f25709a32c738cbd459aa7ee24b0869d9ce16329`. Original author: a73x <dev@a73x.sh>.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
a73x/mux#90
No description provided.