there aren't any other details available besides the snippet below. However, it would seem that it happens when some connection to external service fails so it should be fairly easy to find all such places and handle such situation to avoid crashing
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.992237510Z UNHANDLED PROMISE REJECTION!
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995002150Z Error: socket hang up
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995017540Z at connResetException (node:internal/errors:720:14)
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995031640Z at TLSSocket.socketCloseListener (node:_http_client:474:25)
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995034060Z at TLSSocket.emit (node:events:529:35)
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995036290Z at TLSSocket.emit (node:domain:489:12)
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995038500Z at node:net:350:12
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995040780Z at TCP.done (node:_tls_wrap:657:7) {
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995043060Z code: 'ECONNRESET'
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995045240Z }
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995371122Z Error: socket hang up
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995385902Z at connResetException (node:internal/errors:720:14)
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995388872Z at TLSSocket.socketCloseListener (node:_http_client:474:25)
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995391172Z at TLSSocket.emit (node:events:529:35)
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995393392Z at TLSSocket.emit (node:domain:489:12)
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995396022Z at node:net:350:12
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995399032Z at TCP.done (node:_tls_wrap:657:7) {
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995402272Z code: 'ECONNRESET'
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995408952Z }
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995483432Z Error: socket hang up
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995489662Z at connResetException (node:internal/errors:720:14)
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995492422Z at TLSSocket.socketCloseListener (node:_http_client:474:25)
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995495262Z at TLSSocket.emit (node:events:529:35)
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995498422Z at TLSSocket.emit (node:domain:489:12)
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995501632Z at node:net:350:12
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995504622Z at TCP.done (node:_tls_wrap:657:7) {
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995507742Z code: 'ECONNRESET'
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.995510842Z }
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.996226334Z UNCAUGHT EXCEPTION! NodeCG will now exit.
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:36.996238274Z abort({"code":"ECONNRESET"}). Build with -s ASSERTIONS=1 for more info.
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:37.000236598Z
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:37.000255358Z /nodecg/bundles/nodecg-speedcontrol/node_modules/livesplit-core/livesplit_core.js:8
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:37.000293438Z var Module=typeof LiveSplitCore!=="undefined"?LiveSplitCore:{};var moduleOverrides={};var key;for(key in Module){if(Module.hasOwnPro>
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:37.001505473Z >
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:37.001512413Z abort({"code":"ECONNRESET"}). Build with -s ASSERTIONS=1 for more info.
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:37.001515013Z (Use `node --trace-uncaught ...` to show where the exception was thrown)
gsps-restream-layouts-layouts-1 | 2024-11-02T12:40:37.001517383Z
there aren't any other details available besides the snippet below. However, it would seem that it happens when some connection to external service fails so it should be fairly easy to find all such places and handle such situation to avoid crashing