This website requires JavaScript.
Explore
Help
Sign In
rich
/
visormesh
Watch
1
Star
0
Fork
0
Code
Issues
Pull Requests
Actions
Packages
Projects
Releases
1
Wiki
Activity
Files
main
visormesh
/
palm-client
/
tests
T
Add File
New File
Upload File
Apply Patch
Copy Permalink
Download directory as ZIP
Download directory as TAR.GZ
Delete Directory
History
rich
4b05bf25d5
palm-client: Add Channel's New Key (private channels) fills in a random key from a pool fed by what can't be predicted: the exact tick and position of every pen and key event, and the signal readings of every packet the radio reports. Samples are folded into a SHA-256 pool, a key is a hash of it, and the pool moves on after each; it's kept between launches in an unsaved preference (never in a backup). Until 256 samples have come in, New Key asks for a few seconds of stylus movement. Host-tested in tests/test_entropy.c
2026-11-08 19:38:55 -05:00
..
fixtures.h
palm-client: messaging protocol (send DM/channel, SENT, acks, channels, clock, advert)
2026-11-01 15:21:17 -05:00
replay.c
palm-client: make replay runs the bridge's frame capture through the app's parsers and fails on any frame of a code the app parses that doesn't parse, to catch a firmware layout change before it reaches the Visor. The bridge captures every frame in full with --capture (bridge.sh writes $TMPDIR/visor_frames.txt); captures hold real messages and stay local
2026-11-08 19:32:00 -05:00
test_entropy.c
palm-client: Add Channel's New Key (private channels) fills in a random key from a pool fed by what can't be predicted: the exact tick and position of every pen and key event, and the signal readings of every packet the radio reports. Samples are folded into a SHA-256 pool, a key is a hash of it, and the pool moves on after each; it's kept between launches in an unsaved preference (never in a backup). Until 256 samples have come in, New Key asks for a few seconds of stylus movement. Host-tested in tests/test_entropy.c
2026-11-08 19:38:55 -05:00
test_map.c
palm-client: Map screen with an OSM basemap (tools/make_map.py) and positioned nodes
2026-11-02 12:33:52 -05:00
test_protocol2.c
palm-client: a repeater's "neighbors" reply in its admin console also goes on the Map for 30 minutes: a line from it to each neighbour with a position, solid for SNR 0 dB or better, grey below. Cmds lists the region commands (region, get, allowf, denyf, save)
2026-11-05 15:02:22 -05:00
test_protocol.c
palm-client: tap and hold a message for React, Reply, Send DM and Path Details (also Options > Message Actions for the newest). Reactions use MeshCore One's format (@[Name]<emoji>\n<hash>, hash = Base32 of SHA-256(text || LE timestamp)), so MC1 and MeshMonitor show ours and we show theirs: kept in their own store, shown under the message, never chat or unread. Received messages keep their hash and, matched from the RX log push, the repeaters they came through. The emoji glyphs now go out as the emoji they show, not cp1252 quotes
2026-11-05 09:11:29 -05:00
test_reactions.c
palm-client: tap and hold a message for React, Reply, Send DM and Path Details (also Options > Message Actions for the newest). Reactions use MeshCore One's format (@[Name]<emoji>\n<hash>, hash = Base32 of SHA-256(text || LE timestamp)), so MC1 and MeshMonitor show ours and we show theirs: kept in their own store, shown under the message, never chat or unread. Received messages keep their hash and, matched from the RX log push, the repeaters they came through. The emoji glyphs now go out as the emoji they show, not cp1252 quotes
2026-11-05 09:11:29 -05:00
test_request.c
palm-client: the request retry rules are in request.c (session.c supplies the link), host-tested with a scripted link in tests/test_request.c: a frame that went out is sent again only while tries allows, one that didn't go is resent up to 4 times without using up tries, one cut off part way never is. check_source.py checks that the functions that send over the air or take a queued message (messages, reactions, adverts, syncs, logins, traces) only ever use tries 1
2026-11-08 19:34:16 -05:00
test_sblora.c
palm-client: the module can't keep waking a Visor on failing batteries. A slot power handler (SbPwr, in the copied block) stops the chip interrupting on a low-voltage shutdown, as the Springboard guide asks of modules without LOWBAT*; since the Neo's OS never reports that reason, the wake's card event handler and BgArmWake also check the battery and turn the wake off at the OS's warning level. Host-tested; untested on hardware
2026-11-08 19:27:39 -05:00
test_scopes.c
palm-client: flood scopes (list, radio default, per-channel scope, discover from neighbouring repeaters)
2026-11-02 11:17:44 -05:00
test_screens.c
palm-client: the screens' run-time lines are built in screen_fmt.c, and tests/test_screens.c checks them with their longest values in the large font. That found the Node clock lines running off the edge even in the small font (now 'Visor 11/8 14:02 (UTC-5:00)' and 'Radio 11/8 19:02 UTC, sys 300', a font row apart), Radio Stats lines too long for big counts (they wrap now, and the test checks they still fit above Done; errors get their own line, in hex that shows), and the contact summary and a Trace message too wide ('Room server' is 'Room'). Rows that could still be long are cut instead of running off
2026-11-08 18:53:49 -05:00
test_text.c
palm-client: tap and hold a message for React, Reply, Send DM and Path Details (also Options > Message Actions for the newest). Reactions use MeshCore One's format (@[Name]<emoji>\n<hash>, hash = Base32 of SHA-256(text || LE timestamp)), so MC1 and MeshMonitor show ours and we show theirs: kept in their own store, shown under the message, never chat or unread. Received messages keep their hash and, matched from the RX log push, the repeaters they came through. The emoji glyphs now go out as the emoji they show, not cp1252 quotes
2026-11-05 09:11:29 -05:00