From 21987411324198cf05cced29955e73fbb3a21d94 Mon Sep 17 00:00:00 2001 From: Eric Liu Date: Mon, 7 Sep 2026 21:53:31 -0700 Subject: [PATCH] ci(e2e): run simulator with current meshtastic client, not the stale 2.6.1 pin Meshtasticator's requirements.txt pins meshtastic~=2.6.1, which predates the meshtastic/meshtasticd image it drives; with the old client the simulator never observed node TX packets (both e2e directions timed out). The official meshtastic firmware_harness uses the current client against the same simulator-mode meshtasticd, so install the sim deps with meshtastic floating instead of the pinned requirements file. --- .gitea/workflows/meshtasticator-e2e.yaml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/meshtasticator-e2e.yaml b/.gitea/workflows/meshtasticator-e2e.yaml index d4a0dc0..6f97825 100644 --- a/.gitea/workflows/meshtasticator-e2e.yaml +++ b/.gitea/workflows/meshtasticator-e2e.yaml @@ -71,8 +71,15 @@ jobs: - name: Simulator venv (its own requirements + docker SDK) run: | uv venv --python 3.13 "$HOME/sim-venv" + # NOTE: meshtasticator/requirements.txt pins meshtastic~=2.6.1, which + # predates the meshtastic/meshtasticd image it talks to and never + # observed TX packets (both e2e directions timed out). Install the + # simulator's deps but let meshtastic float to the current client — + # the version the official firmware_harness uses against the same + # meshtasticd simulator mode. uv pip install --python "$HOME/sim-venv/bin/python" \ - -r "$HOME/meshtasticator/requirements.txt" docker + meshtastic numpy matplotlib pandas \ + 'PyPubSub==4.0.3' simpy PyYAML protobuf docker - name: Run Meshtasticator e2e suite run: |