where_is_waldo 0.1.15 → 0.1.16

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 37761c093f1789ab27d7bc83b57b965deb0039a538e1dcef1450bb8680a5328d
-  data.tar.gz: 23fe780af170d951b2b961cc6674224030f1169247a328e1e37b98a16aceb1b3
+  metadata.gz: c5bbdc6480c178670602c5f3749370dced0ef932e99d49c5a753eb3ceef3ed9e
+  data.tar.gz: e8b3d2db9b9179ae9828c7637b772f9f9b9dde5b82cfc1a756c524b8d701694f
 SHA512:
-  metadata.gz: 662057f2eb1431e5b25f74ee89f6fb387748d20526325f7391112b47ce1a6c4ed10d0039341c668eeeb5e78810ed5e4e956c3076673f76c8a0c9d9a57e59c7ff
-  data.tar.gz: 220b4eaf0a42eec12e38e960afae9c0c2dc150e83cd9b2a9cb4d97efd67da9265a49eb5b0f0e399c52105f019faedd0e322cc6dfdec6c839cd2581eef7b03fc0
+  metadata.gz: d92709f8debef9199e51190a7a1952f132af7657faba25d1df174c58e7b841da9fdbd76ad5ef2c50cb922866f49c14306abbe78bfd86cff350564cf819a57715
+  data.tar.gz: 771c824d4eef5c3d02883389dc51ae8197342bb24196d18d00cc07bcba1ba971c654a98a7a285d5d81d574e78d550c28f8a9350212f3da65b38260c2510d7f80

data/CHANGELOG.md

@@ -5,6 +5,51 @@ Notable changes to where_is_waldo. Format loosely follows
 
 ## Unreleased
 
+## 0.1.16 - 2026-11-11
+
+### Fixed
+
+- **A client could stop reconnecting FOREVER, and nothing in ActionCable would
+  turn it back on.** ActionCable's `ConnectionMonitor` is the only thing that
+  reconnects a dropped socket, and it can be switched off permanently:
+
+  ```js
+  close({allowReconnect}) { if (!allowReconnect) { this.monitor.stop() } }
+  stop() { this.stopPolling(); removeEventListener("visibilitychange", ...) }
+  ```
+
+  `stop()` unregisters the very listener that would notice the tab being
+  focused again, and nothing re-registers it. The far end can trigger this
+  from outside the browser: Rails sends a disconnect with `reconnect: false`
+  for an unauthorized or remotely-disconnected connection.
+
+  Observed in production: a socket closed and the tab then ran for SEVEN AND A
+  HALF HOURS -- visible, focused, making ordinary HTTP requests -- without a
+  single further WebSocket attempt. Presence stayed empty the whole time and
+  anything broadcast to online subscribers missed it. Nothing was refused;
+  nothing was attempted.
+
+  There is now a watchdog: while a connection is wanted, waldo notices a
+  monitor that has stopped and starts it again, on a 10-second interval and on
+  its own `visibilitychange` listener. It deliberately does NOTHING while the
+  monitor is running, so it never opens a competing socket or interferes with
+  ActionCable's backoff, and it never undoes a deliberate `disconnectCable()`
+  or a teardown from `configureCable()`.
+
+### Added
+
+- `checkConnection()` is exported. It performs one watchdog pass and returns
+  what it did (`open`, `monitor-running`, `monitor-restarted`, `opened`,
+  `not-wanted`, `no-consumer`, `error`), which makes the recovery path
+  testable and gives an application a way to force a check -- after a resume
+  from sleep, say.
+
+### Changed
+
+- Every read of ActionCable's internals is guarded and returns `error` rather
+  than throwing, so a future rename inside ActionCable degrades the watchdog
+  instead of breaking a consumer's render or heartbeat.
+
 ## 0.1.15 - 2026-11-10
 
 ### Fixed

data/README.md

@@ -81,6 +81,32 @@ configureCable({
 </PresenceProvider>
 ```
 
+### Reconnection
+
+ActionCable reconnects dropped sockets through its own `ConnectionMonitor`, and
+that is still what does the work here. But the monitor can be switched off
+permanently -- `close({allowReconnect: false})` calls `monitor.stop()`, which
+unregisters its `visibilitychange` listener, and nothing in ActionCable
+re-registers it. Rails sends a disconnect with `reconnect: false` for an
+unauthorized or remotely-disconnected connection, so the far end can put a
+browser tab permanently offline.
+
+Since 0.1.16 waldo watches for that: while a connection is wanted it notices a
+stopped monitor and starts it again, on a 10-second interval and on its own
+visibility listener. It does nothing while the monitor is running, so it never
+opens a competing socket, and it never undoes a deliberate `disconnectCable()`.
+
+`checkConnection()` runs one pass on demand and returns what it did, which is
+useful after a resume from sleep or any point an app knows more than a timer
+does:
+
+```jsx
+import { checkConnection } from '@byscott-io/where-is-waldo';
+
+// e.g. after regaining network
+window.addEventListener('online', () => checkConnection());
+```
+
 ### `getToken` and short-lived tokens
 
 `getToken` is called **once per connection attempt**, not once at startup. That

data/VERSION

@@ -1 +1 @@
-0.1.15
+0.1.16

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: where_is_waldo
 version: !ruby/object:Gem::Version
-  version: 0.1.15
+  version: 0.1.16
 platform: ruby
 authors:
 - Scott Gibson