dispatch-rails 0.10.2 → 0.10.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5f742aa0ca8db65f9db9c6b5a135ae7d926fdf57dffde8d1d011ae3449298d32
-  data.tar.gz: e7b3df1d90a904e8c2383a03d3231c0ff7398b4f269632d697c5d728c42c386a
+  metadata.gz: 8dd9b609e2bdb00f81b4b7dc54d47460a9a2d687c51870331459fbbf9019542e
+  data.tar.gz: 33a57685d7ae26719a1aba2871e84fc0cce87159bdf741664dc8169badb5ee5f
 SHA512:
-  metadata.gz: b9cb75b00f87e29843b6837051100d1cac96448ab6db77a048837303b62cd98d18a1ab7dac1bd1f25a8f527b17cf644f2dab6ef46a4a62cf7edc88f1b02d71fd
-  data.tar.gz: f409e09011d0492ccf0ea168ac6f89129ee6fcb83431617a5560ea977c1872a4346586996679538db4b14ea3ae50396d95d47df42f4626f77fff59cd3a00d804
+  metadata.gz: 6d33ec2cc1b41aeb2f1f563c819f91272e8ea3f983b6c9ca638ca152ac9e532014e8b22a5e66d9b947c11506f189d8e6c4f747b6332e8aca08b5d3b5a6422d5f
+  data.tar.gz: 12985b909215d106a6bcda904d031758f276b8f4c8fb766e58f66a6e3672e87d7bdd82951b962389a5bf8877ed4b2706ff88d36aebdb7e1dddd8a195d3b2fa66

data/CHANGELOG.md

@@ -4,6 +4,18 @@ All notable changes to `dispatch-rails` are documented here. The format is based
 on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.10.3] - 2026-07-08
+
+### Fixed
+- The browser error tracker could **report on its own transport failures**. The
+  `send()` fetch had no rejection handler, so a failed report (flaky connection,
+  a blocked or CORS-less endpoint response) surfaced as an `unhandledrejection` —
+  which the tracker's own listener then reported via `send()`, firing another
+  fetch at the same failing endpoint. Hosts saw a `TypeError: Failed to fetch`
+  attributed to `error_tracker.js#send`, and a reachable-but-erroring endpoint
+  could turn it into a self-amplifying loop. The `fetch` now has a `.catch` that
+  swallows transport failures, so the tracker never reports on its own delivery.
+
 ## [0.10.2] - 2026-06-18
 
 ### Fixed

data/app/assets/javascripts/dispatch/error_tracker.js

@@ -156,11 +156,19 @@
     // Preferred: fetch keepalive (proper CORS + Authorization header).
     if (window.fetch) {
       try {
+        // The .catch is essential: fetch reports network/CORS failures as a
+        // REJECTED PROMISE, not a synchronous throw. Without it, a failed report
+        // (flaky connection, blocked endpoint, CORS-less error response) becomes
+        // an unhandledrejection — which our own listener below reports via send(),
+        // firing another fetch at the same failing endpoint. That self-reporting
+        // loop is exactly what "TypeError: Failed to fetch" at send() means.
+        // Swallow transport failures silently; the tracker must never report on
+        // its own transport.
         fetch(cfg.endpoint, {
           method: "POST", keepalive: true, mode: "cors",
           headers: { "Content-Type": "application/json", "Authorization": "Bearer " + cfg.apiKey },
           body: body
-        });
+        }).catch(function () { /* transport failed; never self-report */ });
         return;
       } catch (e) { /* fall through */ }
     }

data/lib/dispatch/rails/version.rb

@@ -1,5 +1,5 @@
 module Dispatch
   module Rails
-    VERSION = "0.10.2".freeze
+    VERSION = "0.10.3".freeze
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: dispatch-rails
 version: !ruby/object:Gem::Version
-  version: 0.10.2
+  version: 0.10.3
 platform: ruby
 authors:
 - Dispatch Team