adam/Remote-Terminal-for-MeshCore
1
0
Fork 0
mirror of https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git synced 2026-08-06 08:43:36 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add note for other bug-finder LLMs about local message ID sub-millisecond collisions

Browse Source
This commit is contained in:
Jack Kingsman
2026-02-23 21:04:29 -08:00
parent 4b84f609b7
commit c6a8c3835c
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
frontend/AGENTS.md
+4
View File
@@ -110,6 +110,10 @@ frontend/src/
- `useRepeaterMode`: repeater login/command workflow
- `useAirtimeTracking`: repeater airtime stats polling
### Local message IDs
`useRepeaterMode` and `useAirtimeTracking` each have a `createLocalMessage` that generates ephemeral (non-persisted) message IDs via `-Date.now()`. Both hooks write to the same `setMessages`, so a same-millisecond call would produce duplicate IDs. In practice this requires a repeater command response and an airtime poll to land in the exact same ms — staggeringly unlikely and cosmetic-only (React duplicate key warning). Not worth fixing.
### Initial load + realtime
- Initial data: REST fetches (`api.ts`) for config/settings/channels/contacts/unreads.