v1.0.40: fix duplicate timer race condition on rapid double-press

onKeyDown is async and calls await startTimer (~1s network). A second
press before that resolves saw the same state (isRunning=false,
memRunningEntryId=null) and created a second Notion entry. Only the
last startTimer call's ID was tracked, orphaning the first entry
running indefinitely in Notion.

pendingKeyDown Set acts as a per-action mutex: a second press while the
first is in-flight is dropped. try/finally guarantees the lock is always
released.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
pdmarf
2026-05-13 18:18:52 +01:00
parent 060a2bc917
commit 6e0976a284
3 changed files with 60 additions and 46 deletions

View File

@@ -1 +1 @@
в<╥!Ъ░xR√з└С;=▀LI" я╓╢HuэF├ы▐Ос─╒┘ sb▌Y╛{йH│╤Н.JщNЦь1╔l
{¿óîj¶? ÍzDA+ÌOÎi °<u,&/Õ+ødeÆá¤"÷œSw+&öO.RC& óä^H-¯