mirror of
https://github.com/meshtastic/Meshtastic-Android.git
synced 2026-04-20 22:23:37 +00:00
Stage 2 of the handshake drains the full node database, which on meshes with 50+ nodes can comfortably exceed the previous 30 s stall guard and trigger a spurious want_config_id retry mid-drain. The meshtastic-client KMP SDK uses a 60 s timeout for this stage for the same reason. Split HANDSHAKE_TIMEOUT into HANDSHAKE_TIMEOUT_STAGE1 (30 s) and HANDSHAKE_TIMEOUT_STAGE2 (60 s) and thread the duration through startHandshakeStallGuard so each call site picks the right value. |
||
|---|---|---|
| .. | ||
| androidMain/kotlin/org/meshtastic/core/data | ||
| commonMain/kotlin/org/meshtastic/core/data | ||
| commonTest/kotlin/org/meshtastic/core/data | ||