Karides aiolo tukendi bildirimi 3 dakikada 14 kez geldi — auto-86 push debounce (PR #644 V F3)

Izmir Alsancak Birinci Kordon Aiolo Balikci sahibi Asli (36), Cuma 20:42 dinner rush ta Apple Watch te 14 ayri "📦 Karides Aiolo tukendi" push notification 3 dakikada. Manager Cemil de ayni 14 ping. Support 4-layer forensic: (1) coklu push subscription? 4+3 = 7 endpoint olur 14 degil. (2) Stock_qty multiple times <=0? D1_MENU karides aiolo 20:38 stock=6, 20:42 dakikasinda 6 concurrent order sirayla decrement etti. (3) Order A basariyla decremented + auto-86 push fired. Order B-F concurrent SELECT te 0 gordu, atomic UPDATE WHERE >= 1 0 row affected (insufficient_stock dondu) ama secondary "stock_qty <= 0" SELECT check her concurrent handler da fired, hepsi ayri push attemped. 6 concurrent fire × 7 endpoint = 42 push attempted; Apple Watch rate-limit suppressed sayisi azalttirdi ama Asli + Cemil her biri 14 surfaced. Bug: atomic stock decrement + auto-86 push iki ayri checkpoint, race condition concurrent handler larin hepsi "stock_qty <= 0" guard ini hit etti. **PR #644 batch V F3** fix: existing cron_idempotency_claims tablosu (originally cron debounce icin) reuse edildi, push fire eden side-effect (restaurant_id, product_id, 5dk window) key li INSERT OR IGNORE atomic claim. Sadece claim kazanan handler push fire eder. 5 dakika sonra claim expire — ayni urun tekrar tukenirse yeni push. Asli pre-fix aylik ~580 push (spam dahil) -> post-fix ~160 (gercek bildirimler). Pattern: state-trigger-driven side effect ((stock_qty <= 0) -> push, (balance <= 0) -> alert, (login_attempts >= 5) -> lockout email) atomic state update ten ayri olarak (entity, time-window) bazli debounce edilmeli. cron_idempotency_claims existing tablo, yeni migration gerek yok.

İlgili makaleler