archie-messaging announces READY=1 before its channels can fail (reviewer finding 4 on 9f6eaccd, proven). install.sh still writes Type=simple, so the READY=1 added in 9f6eaccd is inert today; this bead is the switch that makes it live. (1) internal/app/archiemessaging/compose.go:213 announces after launching the channel goroutines but before any of them binds: internal/channels/webhook/webhook.go:85-92 and internal/channels/email/email.go:67-76 bind inside Start and can return an error BEFORE lifecycle.ReportRunning(), so with a port already in use the process sends READY=1 and then MarkFailed. The three sites this one claims to join all announce AFTER binding (gateway.go:136 after Listen succeeded, state_store.go:157 after both listeners bound, bootstrap.go:1751 after stores/NATS/gateways). Move the announcement to after every channel reports Running through the existing lifecycle hook (channel_status.go:78-83), with a bounded wait so a channel that never reports cannot hang TimeoutStartSec. (2) readiness_notify_test.go:68 composes a service with ZERO channels, so it cannot fail if the announcement moves before the channel loop - it does not pin the property its own doc claims; fix the test in the same commit so it fails for that reason. (3) Unit rules: Type=notify plus NotifyAccess, and do NOT set WatchdogSec - archie-messaging announces but never beats.
Close reason
Integrated on main (d0jp, units/readiness); 8weq items already resolved
Imported from beads archie-core-bkwl · GitHub #1342 · type task · priority P2 · created 2026-09-30 · closed 2026-10-17
archie-messaging announces READY=1 before its channels can fail (reviewer finding 4 on 9f6eaccd, proven). install.sh still writes Type=simple, so the READY=1 added in 9f6eaccd is inert today; this bead is the switch that makes it live. (1) internal/app/archiemessaging/compose.go:213 announces after launching the channel goroutines but before any of them binds: internal/channels/webhook/webhook.go:85-92 and internal/channels/email/email.go:67-76 bind inside Start and can return an error BEFORE lifecycle.ReportRunning(), so with a port already in use the process sends READY=1 and then MarkFailed. The three sites this one claims to join all announce AFTER binding (gateway.go:136 after Listen succeeded, state_store.go:157 after both listeners bound, bootstrap.go:1751 after stores/NATS/gateways). Move the announcement to after every channel reports Running through the existing lifecycle hook (channel_status.go:78-83), with a bounded wait so a channel that never reports cannot hang TimeoutStartSec. (2) readiness_notify_test.go:68 composes a service with ZERO channels, so it cannot fail if the announcement moves before the channel loop - it does not pin the property its own doc claims; fix the test in the same commit so it fails for that reason. (3) Unit rules: Type=notify plus NotifyAccess, and do NOT set WatchdogSec - archie-messaging announces but never beats.
### Close reason
Integrated on main (d0jp, units/readiness); 8weq items already resolved
---
_Imported from beads `archie-core-bkwl` · GitHub #1342 · type task · priority P2 · created 2026-09-30 · closed 2026-10-17_
sam
added the mediumtask labels 2026-10-27 13:39:37 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
archie-messaging announces READY=1 before its channels can fail (reviewer finding 4 on
9f6eaccd, proven). install.sh still writes Type=simple, so the READY=1 added in9f6eaccdis inert today; this bead is the switch that makes it live. (1) internal/app/archiemessaging/compose.go:213 announces after launching the channel goroutines but before any of them binds: internal/channels/webhook/webhook.go:85-92 and internal/channels/email/email.go:67-76 bind inside Start and can return an error BEFORE lifecycle.ReportRunning(), so with a port already in use the process sends READY=1 and then MarkFailed. The three sites this one claims to join all announce AFTER binding (gateway.go:136 after Listen succeeded, state_store.go:157 after both listeners bound, bootstrap.go:1751 after stores/NATS/gateways). Move the announcement to after every channel reports Running through the existing lifecycle hook (channel_status.go:78-83), with a bounded wait so a channel that never reports cannot hang TimeoutStartSec. (2) readiness_notify_test.go:68 composes a service with ZERO channels, so it cannot fail if the announcement moves before the channel loop - it does not pin the property its own doc claims; fix the test in the same commit so it fails for that reason. (3) Unit rules: Type=notify plus NotifyAccess, and do NOT set WatchdogSec - archie-messaging announces but never beats.Close reason
Integrated on main (d0jp, units/readiness); 8weq items already resolved
Imported from beads
archie-core-bkwl· GitHub #1342 · type task · priority P2 · created 2026-09-30 · closed 2026-10-17