Commit c35ee42
committed
fix: register BlueBubbles webhook route before server-info fetch
Previously, monitorBlueBubblesProvider called fetchBlueBubblesServerInfo
(up to 5 s timeout) *before* registering the webhook HTTP route. This
created a window on every startup and after every crash-loop restart
where POST /bluebubbles-webhook returned 404: the plugin HTTP registry
had no matching entry yet so the request fell all the way through the
gateway's stage pipeline.
Fix: move registerBlueBubblesWebhookTarget to the top of the function,
before the async server-info fetch, so the route is reachable as soon
as the provider (re)starts.
Also fix an off-by-one in server-channels restart accounting: when the
crash-loop hit MAX_RESTART_ATTEMPTS + 1 it was reporting
reconnectAttempts = MAX + 1 instead of MAX, causing the snapshot to
show one extra attempt than the configured cap.
Fixes #456201 parent e84266e commit c35ee42
File tree
2 files changed
+19
-11
lines changed- extensions/bluebubbles/src
- src/gateway
2 files changed
+19
-11
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
269 | 269 | | |
270 | 270 | | |
271 | 271 | | |
272 | | - | |
| 272 | + | |
| 273 | + | |
| 274 | + | |
| 275 | + | |
| 276 | + | |
| 277 | + | |
| 278 | + | |
| 279 | + | |
| 280 | + | |
| 281 | + | |
| 282 | + | |
| 283 | + | |
| 284 | + | |
| 285 | + | |
| 286 | + | |
273 | 287 | | |
274 | 288 | | |
275 | 289 | | |
| |||
285 | 299 | | |
286 | 300 | | |
287 | 301 | | |
288 | | - | |
289 | | - | |
290 | | - | |
291 | | - | |
292 | | - | |
293 | | - | |
294 | | - | |
295 | | - | |
296 | | - | |
297 | 302 | | |
298 | 303 | | |
299 | 304 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
258 | 258 | | |
259 | 259 | | |
260 | 260 | | |
261 | | - | |
| 261 | + | |
| 262 | + | |
| 263 | + | |
| 264 | + | |
262 | 265 | | |
263 | 266 | | |
264 | 267 | | |
| |||
0 commit comments