$ the-wire · showcase
URI encoding without the temporary binaries, faster local integration tests
By RepoJournal · Filed · About Elixir & Phoenix · Composed from the cited sources · methodology
Elixir's URI encoder now writes encoded bytes straight into the output binary instead of allocating a throwaway binary per input byte, and Phoenix's local integration test workflow got the same treatment CI did.
Encode URIs with a single accumulator (#15979) elixir-lang/elixir
The encoder now writes encoded bytes directly to the output binary rather than building a temporary binary for every input byte, which cuts both allocation and peak memory for URI-heavy code paths. The author reports it is faster with no performance regressions on his machine.
Improve local integration test workflow phoenixframework/phoenix
Cold local integration runs land around 3m30s (image download, build, fresh compilation) and about 2m10s on subsequent runs on the author's machine, following the earlier CI-side work that cut CI time and improved observability. The test summary pipeline was reworked to serve both local single-job and CI multi-job runs from one structure.
Improve local integration test workflow (#6873) phoenixframework/phoenix
Database container healthchecks now probe over TCP with startup intervals, because MySQL and PostgreSQL bootstrap servers during first boot listen only on Unix domain sockets and made socket-based pings report healthy before the real server was up. If you copy these compose healthchecks for your own Phoenix integration setup, the TCP probe is the part worth taking.