fishcakez/acceptor_pool

This system is a mature Erlang library providing a robust TCP acceptor pool with supervisor-style lifecycle management. It focuses on high availability and stability by gracefully handling transient network errors, preventing aggressive restart loops, and offering detailed connection tracking. Recent efforts have centered on refining error handling, improving interface monitoring, and simplifying build dependencies for its example applications.

12 changes.

This period focused on the initial release and refinement of the acceptor\_pool library, introducing a TCP acceptor architecture with supervisor-style management. Significant effort was dedicated to refactoring the acceptor lifecycle, enhancing socket error handling, and enabling code reloading capabilities. Comprehensive testing was implemented to cover the pool's lifecycle, supervision, and introspection features, alongside an example telnet echo application demonstrating graceful connection handling.

2 changes.

The project expanded its continuous integration pipeline to support multiple Erlang/OTP versions and enforced stricter code quality checks using xref and dialyzer. Concurrently, the test suite for the acceptor pool was updated to reflect implementation changes, including the removal of permanent restart policy tests and the addition of interface monitoring verification.

1 change.

The telnet\_echo example no longer fetches the acceptor\_pool dependency from a remote Git repository; it now relies on the local or globally available package, simplifying the build setup.

1 change.

The acceptor pool now handles transient connection errors (such as \enotconn\) gracefully without killing the listen socket, ensuring higher availability under load. It also provides more detailed connection information by including the specific listening socket name in accept messages when bound to \0.0.0.0\, allowing users to identify which interface accepted a connection. Additionally, the pool now returns the acceptor process ID upon socket acceptance, enabling direct process control, and restricts acceptor restart policies to \transient\ or \temporary\ to prevent aggressive restart loops on persistent errors.

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 30 → 35 (+4.7)
• Rubric changed (rubric-2026.09.12 → rubric-2026.09.18) — scores are not directly comparable.

• Code Health 97 → 97 (+0.0)
• Architecture 69 → 69 (+0.0)
• Maturity 27 → 43 (+16.1)
• Readiness 60 → 64 (+4.1)
• Security 67 → 67 (+0.0)
• Event-Driven 10 → 10 (+0.0)

• Coverage not measured — no coverage collector is wired up
• Documentation: no usage examples (examples/telnet_echo/README.md)

• Dependency hygiene PARTLY measured — rebar3 pinning read, dependency currency not (no rebar.lock-pinned Hex declaration to grade)
• Unbounded dependency requirement: acceptor_pool

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

fishcakez/acceptor_pool was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.