#debounce
🟠 DeBounce is reporting a Partial Outage since 03:23 UTC

"Bulk Validation API is down"

Affects: Bulk Validation API

Live timeline → https://pingoru.io/providers/debounce/incidents/12483923?utm_source=bluesky&utm_content=inc-12483923

#DeBounce #DeBounceDown
DeBounce: Bulk Validation API is down · November 13, 2026 · Pingoru
DeBounce incident on November 13, 2026: Bulk Validation API went down. Started 3:23 AM UTC, resolved ongoing (● 6m). Affected: DeBounce (Bulk Validation API).
pingoru.io
November 13, 2026 at 3:30 AM
A BLE rotary encoder inside a peppergrinder is basically an oversized tactile scroll wheel already. You just need a debounce timer so the peppercorns shifting inside don't register as extra timeline scrubs.
November 12, 2026 at 2:08 PM
🟢 Update: DeBounce marked this resolved at 03:34 UTC.

Duration: 11m.
November 13, 2026 at 3:36 AM
Cheap mechanical EC11 encoders chew through their detent springs fast once you start cranking a timeline through them. Swapping to an optical encoder or a magnetic Hall sensor holds up much better to heavy scrolling and cuts out half the debounce noise.
November 12, 2026 at 4:09 AM
this is why you debounce URL updates
November 11, 2026 at 12:14 AM
i'm learning about debounce functions and not to be too dramatic but i'm going to light myself on fire
November 8, 2026 at 3:34 AM
Kolom pencarian yang mengirim tiap huruf: 10 ketukan, 10 permintaan.

Debounce: tiap ketukan menyalakan timer 300 ms dan membatalkan timer sebelumnya, jadi cuma 1 yang terkirim.

https://learnhypersheets.com/learn/javascript/events
November 10, 2026 at 5:00 AM
Kotak pencarian di aplikasimu sudah pakai debounce, atau masih kirim tiap huruf?
November 10, 2026 at 5:00 AM
Ed Davey, once again following the other parties; demanding Lib Dem Cllrs stop working with Greens if they don’t debounce the Zionism is Racism motion.
Thankfully there are some sensible Lib Dems. In B’ham they are focused on delivering commitments set out in Fairer Birmingham Partnership Agreement
November 7, 2026 at 8:08 AM
うーん、Arduinoキーヤーにサイドトーン付けてちょっと叩いてみたけど…以外にeager debounceの効果はあるんじゃないかなあ。文字の最後にうっかりヘンなのを叩く、というのが減った気が。気のせいかもだけど。

ちょっとこれはしばらく使ってみるとして、ブレッドボードで組んだ部分はユニバーサル基板で組み直す必要がありそう。
November 8, 2026 at 7:38 AM
El doble clic que empeora suele ser el interruptor gastado, no Windows. Un test muestra si una pulsación se convierte en dos a pocos ms. Si es así, subir el debounce en el software puede aguantar hasta el recambio: fixmint.cc/es/mouse-test
November 8, 2026 at 12:28 PM
Your setTimeout Didn't Break — Chrome Killed It
The log said the sync was scheduled. Two minutes later, nothing had run. No error, no rejected promise, no missed callback warning — just a line that promised future work and a database that never changed. Here is the excerpt that ended a week of blaming my own debounce logic: [10:41:02] change detected [10:41:02] sync scheduled in 120000ms [10:41:32] service worker terminated (idle) The timer did not fail. The process that owned it was shut down, and a `setTimeout` cannot outlive its process. **The short version** * `setTimeout` is a handle in the worker's heap. Terminate the worker and the handle is gone. * MV3 kills an idle background worker after about 30 seconds, no matter what is pending. * Persist the _due time_ , not the timer, and re-arm it when the worker wakes. ## Three suspects that were innocent **The debounce.** The code coalesced rapid changes into one sync two minutes later. It worked in tests because I kept clicking things, which kept the worker alive. In production, users typed once and walked away. **A stale closure.** I rewrote the callback twice looking for a captured variable. The closure was fine. It simply never executed. **Storage quota.** I added error handling around `chrome.storage` and saw nothing, because nothing was written. The write happened inside the callback that never ran. The pattern behind all three: I was debugging JavaScript semantics when the failure was in the execution model. ## What MV3 actually guarantees Chrome keeps a background service worker alive while it is handling events. When the event queue goes quiet for roughly 30 seconds, the worker is terminated. A single event may run for up to five minutes, but pending timers do not count as activity. That means a timer longer than the idle window is a coin flip. It survives only if something else — a message, a click, an API call — keeps waking the worker before the reaper arrives. In a quiet extension, nothing does. ## Fix 1: store the deadline, arm an alarm This is the default answer and it covers most features: const KEY = 'pending-sync-at'; const ALARM = 'pending-sync'; async function scheduleSync(delayMs: number) { const dueAt = Date.now() + delayMs; await chrome.storage.local.set({ [KEY]: dueAt }); await chrome.alarms.create(ALARM, { when: dueAt }); } chrome.alarms.onAlarm.addListener(async (alarm) => { if (alarm.name !== ALARM) return; const stored = await chrome.storage.local.get(KEY); if (!stored[KEY]) return; await chrome.storage.local.remove(KEY); await runSync(); }); chrome.runtime.onStartup.addListener(() => void recover()); Two details matter. `alarms.create({ when })` takes an absolute timestamp, so a worker restart does not shift the deadline. And the alarm handler clears the stored key before running the work, which prevents a duplicate run if the alarm fires twice. ## Fix 2: run the delay where the user already is If the sync only matters while a tab is open, move the debounce into the content script. The page owns that timer, the worker is not involved, and closing the tab cancels work that no longer has a reason to exist. This is not a workaround; it is the right lifetime for UI-scoped work. ## Fix 3: keep the worker warm (and accept the cost) A message every 20 seconds keeps the idle timer from expiring. It also burns battery, keeps a process alive for no user benefit, and is the first thing a Chrome Web Store reviewer asks about. I have used it for a short migration window. I would not ship it as architecture. ## Fix 4: move the plumbing into the build If the codebase has dozens of timer call sites, rewriting each one by hand is how regressions multiply. `vite-mv3-sw-compile-persist` rewrites long `setTimeout`/`setInterval` calls into alarm-backed wrappers at build time and restores marked state on wake. It requires Vite 8+, the `storage` permission and `alarms` when long timers are present; destructured variables and anonymous callbacks that capture locals are not recoverable, so the source still needs some discipline. One more nuance: extension API calls reset the idle timer, so a worker that is making a request is not necessarily idle. Do not rely on that as a design, but it explains why a timer sometimes survives a burst of activity and dies in a quiet minute. ## With and without the plugin The before/after from the plugin's README is the whole argument: **Without`vite-mv3-sw-compile-persist`** let count = 0; chrome.action.onClicked.addListener(async () => { const stored = await chrome.storage.session.get('count'); count = (stored.count as number) ?? 0; count++; await chrome.storage.session.set({ count }); }); chrome.alarms.create('cleanup', { delayInMinutes: 5 }); chrome.alarms.onAlarm.addListener((alarm) => { if (alarm.name === 'cleanup') cleanup(); }); **With`vite-mv3-sw-compile-persist`** let count = 0; chrome.action.onClicked.addListener(() => { count++; }); setTimeout(cleanup, 5 * 60_000); The second version is the code you meant to write. The plugin adds restore, dirty tracking, a debounced flush and alarm-backed timers at build time — no runtime import, no wrapper API. **Repository:** vite-mv3-sw-compile-persist If this saved you the afternoon I lost, a star on the repo is a fair trade — and it helps the next person find the explanation before the workaround. What is the longest delay your extension promises, and what happens to that promise when the worker dies at second 30?
dev.to
November 10, 2026 at 6:38 PM
UI state conflicts between virtual lists and instant search indexing are real. What the poster missed is the debounce timer resetting mid-keystroke on slow focus events. Microsoft is right to push unified navigation, but stealing focus from the input is an unforgivable mechanical bug.
November 8, 2026 at 10:17 AM
Oof, that's usually a worn switch, not Windows acting up. Click around on a tester and watch whether one press becomes two a few milliseconds apart. If it does, raising debounce in the mouse software can buy you time: fixmint.cc/mouse-test
November 8, 2026 at 7:09 AM
That's the switch wearing out, not you. A click chatter test shows how bad it is (two clicks a few ms apart = worn switch). Many mice let you raise debounce time in their software as a stopgap until you swap the switch: fixmint.cc/mouse-test
November 8, 2026 at 2:39 AM
Speaking of, having gotten 𝙍𝙊𝘽𝙐𝙎𝙏𝙇𝙔 𝙈𝙀𝙏𝙄𝘾𝙐𝙇𝙊𝙐𝙎 at package inspection over the previous SLDC iterations, we are now at a point where diagnostics work symbiotically with our test suites to unpack these teenie...details.

Nefarious and nested little diddies, often the ones creating the most...fun.
November 13, 2026 at 7:05 PM
Don’t denounce the debounce, dude!
November 3, 2026 at 6:50 PM
I don't have any good measurements on before/after, but anecdotally it feels a bit slower from UK/Finland. The first request for a query string is often ~1s, while repeats are like 300ms. I switched shelf from using debounce to throttle and that mitigated it a bit
November 4, 2026 at 6:05 PM
JW_MatrixButtons (1.0.7) by JW Control

➡️ https://github.com/JW-Control/JW_MatrixButtons

Button scanner with matrix and direct modes, debounce, press/release/repeat events and HMI/PLC helpers.

#ArduinoLibs #ArduinoLibraries
GitHub - JW-Control/JW_MatrixButtons: Librería Arduino para lectura de matrices de botones con debounce, eventos (press/release/repeat) y navegación tipo HMI/PLC.
Librería Arduino para lectura de matrices de botones con debounce, eventos (press/release/repeat) y navegación tipo HMI/PLC. - JW-Control/JW_MatrixButtons
github.com
November 3, 2026 at 2:10 PM
AlashButton (1.0.1) by Alash Electronics

➡️ https://github.com/Alash-electronics/AlashButton

Easy button library: debounce, click, double click, long press and hold-repeat without delay(). Many buttons, clear tips, no dependencies.

#ArduinoLibs #ArduinoLibraries #AITainted
GitHub - Alash-electronics/AlashButton: Easy button library: debounce, click, double click, long press and hold-repeat without delay(). Many buttons, clear tips, no dependencies.
Easy button library: debounce, click, double click, long press and hold-repeat without delay(). Many buttons, clear tips, no dependencies. - Alash-electronics/AlashButton
github.com
November 3, 2026 at 2:40 PM
Buttons (1.0.0) by Serhii Lebedenko

➡️ https://github.com/SerhiiLe/Buttons

Lightweight, zero-dependency button library with debounce, multi-clicks, hold, step, and custom event sources.

#ArduinoLibs #ArduinoLibraries
GitHub - SerhiiLe/Buttons: A lightweight, zero-dependency C++ library for handling buttons,
A lightweight, zero-dependency C++ library for handling buttons, - SerhiiLe/Buttons
github.com
November 4, 2026 at 2:30 AM
RFID plus ESP8266 is a solid combo, but I’d still add a debounce delay in code—otherwise stray tag reads will drive you mad debugging false unlocks.
November 3, 2026 at 7:39 AM
throttlebeam 0.2.0 [updated]

Keyed debounce, throttle and idempotency primitives on OTP.

Licenses: MIT
October 31, 2026 at 8:04 PM
kinTを実際に使えるようにマップを変えてみたり調整してみたけど、スイッチが劣化してきているのかチャタリングがそこそこ出る。とりあえずdebounceを40msと長くして誤魔化した…
November 1, 2026 at 4:03 PM