Uncaught TIMEOUT

[rafaelromcar-parabol]

Issue - Bug

• How serious is the bug? P3?
• OS: macOS / Linux / Windows / ?
• Browser: Chrome / Safari / Lynx / ? + version
• Node version: node --version
• NPM version: npm --version
• Parabol v8.12.3

Seen right after a release

{"time":"2024-12-13T09:43:17.005Z","level":"info","message":"\n🔥🔥🔥 Server ID: 176. Ready for Sockets: Port 3000 🔥🔥🔥 []"}                                                                                     
(node:1) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.                         
(Use `node --trace-deprecation ...` to show where the warning was created)                                                                                                                                         
{"time":"2024-12-13T09:43:27.571Z","level":"info","message":"SEND TO SENTRY [\n  Error: GQL executor took too long to respond\n      at publishInternalGQL (/home/node/parabol/dist/web.js:188754:43)\n      at asy
{"time":"2024-12-13T09:43:35.970Z","level":"info","message":"SEND TO SENTRY [\n  Error: TIMEOUT\n      at Timeout._onTimeout (/home/node/parabol/dist/web.js:185218:16)\n      at listOnTimeout (node:internal/time
{"time":"2024-12-13T09:43:35.976Z","level":"info","message":"SEND TO SENTRY [\n  Error: TIMEOUT\n      at Timeout._onTimeout (/home/node/parabol/dist/web.js:185218:16)\n      at listOnTimeout (node:internal/time
{"time":"2024-12-13T09:43:35.979Z","level":"info","message":"SEND TO SENTRY [\n  Error: TIMEOUT\n      at Timeout._onTimeout (/home/node/parabol/dist/web.js:185218:16)\n      at listOnTimeout (node:internal/time
{"time":"2024-12-13T09:43:36.495Z","level":"info","message":"SEND TO SENTRY [\n  Error: GQL executor took too long to respond\n      at Object.publishInternalGQL [as default] (/home/node/parabol/dist/web.js:1887
{"time":"2024-12-13T09:43:37.590Z","level":"info","message":"SEND TO SENTRY [\n  Error: GQL executor took too long to respond\n      at publishInternalGQL (/home/node/parabol/dist/web.js:188754:43)\n      at run
{"time":"2024-12-13T09:43:37.591Z","level":"info","message":"SEND TO SENTRY [\n  Error: GQL executor took too long to respond\n      at publishInternalGQL (/home/node/parabol/dist/web.js:188754:43)\n      at asy
{"time":"2024-12-13T09:44:11.670Z","level":"info","message":"SEND TO SENTRY [\n  Error: TIMEOUT\n      at Timeout._onTimeout (/home/node/parabol/dist/web.js:185218:16)\n      at listOnTimeout (node:internal/time
{"time":"2024-12-13T10:00:10.354Z","level":"info","message":"SEND TO SENTRY [\n  Error: GQL executor took too long to respond\n      at Object.publishInternalGQL [as default] (/home/node/parabol/dist/web.js:1887
{"time":"2024-12-13T10:00:11.049Z","level":"info","message":"SEND TO SENTRY [\n  Error: TIMEOUT\n      at Timeout._onTimeout (/home/node/parabol/dist/web.js:185218:16)\n      at listOnTimeout (node:internal/time
{"time":"2024-12-13T10:00:12.074Z","level":"info","message":"SEND TO SENTRY [\n  Error: TIMEOUT\n      at Timeout._onTimeout (/home/node/parabol/dist/web.js:185218:16)\n      at listOnTimeout (node:internal/time
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:                   
Error: TIMEOUT                                                                                                                                                                                                     
    at Timeout._onTimeout (/home/node/parabol/dist/web.js:185218:16)                                                                                                                                               
    at listOnTimeout (node:internal/timers:581:17)                                                                                                                                                                 
    at process.processTimers (node:internal/timers:519:7)                                                                                                                                                      

Acceptance Criteria (optional)

Users can:

• Do this
• Do that
• Cannot do that
  Triage is performed to find the root cause of the bug, timeboxed to ~1 hour.

Estimated effort: 1 hour to triage. More if root cause is already identified.