Desk channel: keep what was shown in memory while the store does not answer, so a clearing replaces the urgent notification (issue 384) #490

Merged

mesh-tools merged 2 commits from fix/desk-clear-lost into main 2026-10-26 11:33:48 +00:00

Conversation 1 Commits 2 Files Changed 3

+165 -10

2 Commits

Author	SHA1	Message	Date
jschoubben	a30c168512	desk-channel: take the work when the store does not answer, and keep what it holds at the next work and the minute's standing ... Review round 1: offering the work again let a redelivered raise follow its own clearing and replace it, and a redelivery is bounded where an outage is not. The work is now taken; what was shown stays in memory, recalled first, and is kept at the start of the next work and at the minute's standing, stopping at the first write the store does not answer. A desk that restarts before then loses where those are shown, and its log said how many it held.	2026-10-26 11:46:21 +01:00
jschoubben	f885250913	desk-channel: keep where a message is shown when the store does not answer, so its clearing still replaces it ... On 2026-10-26 09:18 the bus reloading its accounts made the desk's state store answer 'no responders' just as the urgent 'A new build of mesh-controller cannot be delivered' was shown. The desk logged that it could not keep the notification ids and acked the work; the router's clearing at 09:34 then found no record, was shown as a new notification, and the urgent one stayed on the operator's screen for hours. Now what was shown and not kept is held in memory, recalled before the store by edits, reminders, clicks and a notifier restart, kept at the next piece of work, and its work is offered again until the store keeps it, without being shown twice. An edit of a message nothing records is said in the journal.	2026-10-26 11:46:09 +01:00