Handling and recovery of INTERNAL_ERROR types of errors in connecting to external application sockets in NodeJS #404
Description
As you know and from the issues that have been opened, there is a huge amount of problems related to such errors:
Error Processing Request (please open an issue https://github.com/Danny-Dasilva/CycleTLS/issues/new/choose) ->
2025/09/15 07:14:53 Socket Errorwebsocket: close 1006 (abnormal closure): unexpected EOF
2025/09/14 04:55:50 Read error: stream error: stream ID 1; INTERNAL_ERROR
reset err: cancel stream code: CANCEL StreamID: 1
Or earlier:
2025/08/14 20:30:35 Read error: context deadline exceeded
2024/08/17 02:55:03 Request Failed: context deadline exceeded (Client.Timeout or context cancellation while reading body)
2024/04/11 09:18:55 Unmarshal Errorjson: cannot unmarshal number into Go struct field Options.options.headers of type string
2024/04/11 00:57:30 Unmarshal Errorjson: cannot unmarshal object into Go struct field Options.options.body of type string
These errors have become very frequent and annoying and have made the program unstable and unreliable to the point where it has made me think of replacing it!
Since there is no progress in solving these errors and there does not seem to be a fundamental and root solution, my suggestion is to provide a solution where at least we can catch and manage these errors so that the program can recover itself.
Because right now they suddenly appear in my console and my cycleTLS object gets corrupted and I cannot notice this from the code even though I have put it in a try/catch block.
Even when I try to check it periodically, I still do not know how to revive the corrupted cycleTLS object because the newly created object still cannot communicate with index.exe.
Even when I try to kill and re-run index.exe in the program, my program still cannot connect to it.
In short, assuming that the errors mentioned above are not solvable at this time, please give your ideas and comments on this matter, error handling, and object recovery.