meshcore-client

Commit Graph

Author	SHA1	Message	Date
Strycher	6047a02a6e	fix(#82 ): skip empty channel slots on RESP_CODE_ERR instead of timing out The firmware answers RESP_CODE_ERR for an empty/invalid channel index, but _handleErrorFrame never advanced the in-flight channel sync. So every empty slot waited out the 2s timeout + 3 retries (~8s each): a device with a few populated channels out of a large capacity took minutes to sync (~40 slots requested, ~29 empty -> ~4 min) before the real channels (which answer CHANNEL_INFO) finally synced in the last couple seconds. Now an ERR that lands while a channel GET is in flight (and no generic-ack command is waiting -- that one is order-correlated to the ERR first) advances to the next slot immediately, mirroring the CHANNEL_INFO success path minus adding a channel. The decision is pinned as a pure static predicate and tested, matching the connector's existing decision-helper test convention. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	1 month ago
Strycher	be33f4ff5f	fix(#71 ): testable offband_caps read + byte-82 offset verification (N1) Gemini MAJOR #4 (offset unverified / short-frame robustness): - Offset VERIFIED against firmware MyMesh.cpp: the device-info tail is three consecutive out_frame[i++] writes -- client_repeat@80, path_hash_mode@81, offband_caps@82. Bytes 80/81 are shipping (path-hash), so caps@82 is correct by adjacency, not a guess. - Extracted MeshCoreConnector.parseOffbandCaps (pure, bounds-checked) so the guard + offset are unit-testable; _handleDeviceInfo delegates to it. - 4 tests pin: pre-v14 short frame -> null, len-83 reads byte 82 verbatim, observer bit round-trips supportsConfig, hostile truncated frames never OOB. Live observer node confirms end-to-end at G2. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	1 month ago
Strycher	ce9126fbc6	test(#68 ): adversarial codec test suite (A1, TDD-RED) 11 tests for ObserverConfigClient / BrokerListDecoder. 9 green (builders, response parsing, happy-path decode, malformed-NUL, garbage-numeric, stray-KV). 2 RED BY DESIGN, documenting the Gemini findings to be fixed by C1 (#72): - DoS: BrokerListDecoder retains 256 slots from a hostile BROKER_KV flood (must bound to brokerSlotCount=10). - out-of-range slot 200 is stored (must be dropped). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	1 month ago
Strycher	5227507810	fix(#25 ): SNR-first repeater ranking (recency as a sub-dB tie-breaker) DirectRepeater.ranking added recencyScore (0..1.8M) to the SNR term (1000/dB), so recency dominated (~1 dB == 1 second), contradicting the comment that recency only breaks ties. Scale recency to a 0-999 bonus so SNR (1000/dB) is primary and recency only decides sub-dB ties. Offset SNR by its floor (+32; SX126x SNR spans -32..+31.75 dB) so every live ranking stays >= 0, above the -1 stale sentinel; otherwise the scaled-down recency leaves live rankings negative and a stale repeater would outrank a live one. Adds DirectRepeater.ranking tests: SNR-first, recency tie-break, stale=-1, live-always-outranks-stale. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	1 month ago
kingult	dfcf13a97b	fix: lat/lon double-write in buildUpdateContactPathFrame The function emitted two consecutive 8-byte position blocks instead of one, producing a frame 8 bytes longer than the documented layout. When a caller passed lastModified, the firmware parsed the duplicated second lat as the timestamp, giving wildly wrong "last seen" values on imported contacts. Delete the unconditional first block; keep the conditional block that correctly skips the optional tail when neither location nor lastModified is set, zero-fills position slots when only lastModified is present, and appends the optional timestamp. Adds test/connector/build_update_contact_path_frame_test.dart with five cases covering all four optional-tail combinations plus the fixed-point lat/lon encoding. Fixes #427	3 months ago
just-stuff-tm	2f770bbd53	fix(tcp): reset state on aborted pre-handshake connect	5 months ago
just-stuff-tm	9db79e9d40	test(tcp): harden cancel-race handling and add coverage - tighten late TCP connect error suppression to manual-cancel disconnecting/disconnected windows - keep TCP handshake failures surfaced outside explicit cancel flow - allow TcpScreen connect action when connector is scanning - add connector-level tests for late-error suppression classifier - add TcpScreen test covering connect from scanning state	5 months ago

7 Commits (d3d293a3005baa8e58a2bfe2c87e0290fb07d87a)