search

phetsims / aqua

Automatic QUality Assurance
MIT License
2 stars 4 forks source link

Handle 414 errors #182

Closed zepumph closed 1 year ago

zepumph commented 1 year ago

The firefox is giving errors, I believe because the headers are too long:

48|ct-node | You have triggered an unhandledRejection, you may have forgotten to catch a Promise rejection:
48|ct-node | Error: Request failed with status code 414
48|ct-node |     at createError (/data/share/phet/continuous-testing/ct-node-client/aqua/node_modules/axios/lib/core/createError.js:16:15)
48|ct-node |     at settle (/data/share/phet/continuous-testing/ct-node-client/aqua/node_modules/axios/lib/core/settle.js:17:12)
48|ct-node |     at IncomingMessage.handleStreamEnd (/data/share/phet/continuous-testing/ct-node-client/aqua/node_modules/axios/lib/adapters/http.js:322:11)
48|ct-node |     at IncomingMessage.emit (node:events:525:35)
48|ct-node |     at endReadableNT (node:internal/streams/readable:1359:12)
48|ct-node |     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
zepumph commented 1 year ago

We can increase the size with this, but first we should understand the problem better. It has only happened a few times though for the firefox client, so let's try to reproduce first.

zepumph commented 1 year ago

This is likely not causing too much trouble, but I will note https://github.com/phetsims/aqua/issues/178 as the parent issue.

zepumph commented 1 year ago

This isn't worth keeping open given how rarely it is occurring, if it pops up more often, we will reopen.

zepumph commented 1 year ago

There are a few more of these over on bayes:

[phet-admin@bayes logs]$ cat /home/phet-admin/.pm2/logs/ct-node-puppeteer-client-out-*.log  | grep "code 414"
2023-05-15T12:31:55: Fatal error: Request failed with status code 414
2023-05-15T18:16:44: Fatal error: Request failed with status code 414
2023-05-16T03:28:02: Fatal error: Request failed with status code 414
2023-05-16T08:16:41: Fatal error: Request failed with status code 414
2023-05-15T14:13:11: Fatal error: Request failed with status code 414
2023-05-15T20:43:23: Fatal error: Request failed with status code 414
2023-05-17T17:45:54: Fatal error: Request failed with status code 414
2023-05-18T08:12:01: Fatal error: Request failed with status code 414
2023-05-16T10:49:30: Fatal error: Request failed with status code 414
2023-05-17T10:27:55: Fatal error: Request failed with status code 414
2023-05-14T22:09:35: Fatal error: Request failed with status code 414
2023-05-16T04:01:17: Fatal error: Request failed with status code 414
2023-05-16T14:53:44: Fatal error: Request failed with status code 414
2023-05-15T14:21:26: Fatal error: Request failed with status code 414
2023-05-16T16:00:31: Fatal error: Request failed with status code 414
2023-05-15T12:25:22: Fatal error: Request failed with status code 414