Migrating from mob_dev 0.5.11 → 0.6.13, a device-deploy mix task broke at compile:
warning: MobDev.Tunnel.setup/2 is undefined or private. Did you mean: setup/1
lib/mix/tasks/.../two_device_mesh.ex:105
MobDev.Tunnel.setup/2 (device, index) became setup/1 (device) — the dist port is now assigned internally (deterministic per-serial), so the caller no longer passes an index. The change itself is good, but it isn't in the 0.6.x CHANGELOG (which otherwise tracks breaks, e.g. the 0.6.13 zig note).
Ask: a CHANGELOG entry for the Tunnel.setup arity change — and ideally a quick scan for other public MobDev.* arity changes across the 0.6 line — would smooth 0.5 → 0.6 migrations.
Our fix was simply dropping the index arg and the now-pointless Enum.with_index.
Migrating from
mob_dev0.5.11 → 0.6.13, a device-deploy mix task broke at compile:MobDev.Tunnel.setup/2(device, index)becamesetup/1(device)— the dist port is now assigned internally (deterministic per-serial), so the caller no longer passes an index. The change itself is good, but it isn't in the 0.6.x CHANGELOG (which otherwise tracks breaks, e.g. the 0.6.13 zig note).Ask: a CHANGELOG entry for the
Tunnel.setuparity change — and ideally a quick scan for other publicMobDev.*arity changes across the 0.6 line — would smooth 0.5 → 0.6 migrations.Our fix was simply dropping the index arg and the now-pointless
Enum.with_index.