erldistpy/tests
russell@unturf.com 35d0eca342
tests: Mix release + TLS dist + OTP 25 + Wallet.Bridge GenServer (passes)
Closes the loop on docker-based repro: builds a real Elixir Mix release
(with :ssl included) containing one GenServer registered as
Elixir.Wallet.Bridge, runs it under TLS dist with the production
inet_tls.conf shape, hits it from erldistpy.Node.call.

Passes cleanly with erldistpy 0.1.7. So the production portal failure
('peer closed after 0/4 bytes' against portal@unsandbox.com) isn't
reproducible in isolation, even with every dimension matched (Mix
release, OTP 25, TLS dist with permissive verify_fun + tls1.2/1.3 +
secure_renegotiate, Elixir GenServer, long FQDN node names).

The bug must be in interaction with portal's other dist connections or
its larger supervisor tree — beyond what we can repro without standing
up the full portal app locally.
2026-06-17 09:57:12 -04:00
..
__init__.py phase 0 + 1: repo bones and ETF codec 2026-06-16 10:39:01 -04:00
test_channel.py 0.1.7: declare DFLAG_MANDATORY_25_DIGEST + decode dist-header replies 2026-06-17 08:51:09 -04:00
test_epmd.py phase 2: EPMD client 2026-06-16 11:00:00 -04:00
test_etf.py etf: add MAP_EXT (tag 116) for Erlang/Elixir maps 2026-06-16 12:16:35 -04:00
test_handshake.py phase 3: v6 distribution handshake 2026-06-16 11:08:28 -04:00
test_node.py phase 5: Node.call() gen_server protocol 2026-06-16 11:33:28 -04:00
test_node_mix_release.py tests: Mix release + TLS dist + OTP 25 + Wallet.Bridge GenServer (passes) 2026-06-17 09:57:12 -04:00
test_node_otp26.py tests/test_node_otp26: portal-match TLS config + long node names + container stdout capture 2026-06-17 09:32:17 -04:00
test_tls.py phase 6: TLS dist via inet_tls_dist 2026-06-16 12:06:07 -04:00