Unable to catch errors | electronjs.org | Page 1

runic swan Jun 8, 2023, 7:02 PM

#

I am using Electron net request module to send requests. Sometimes requests might fail for various reasons and they pop an error in the app. For this reason i used uncaughtException handler to catch them. I need somehow to do try{}catch() on top of this request handle and to be able to catch the request because this request is being executed in an async function and i cant afford it to become a zombie or just stop working. I need to know when some async function stops working because of this and which one it is. How can i possibly catch this error because try catching this request doesnt work?

I simply send the request inside

async function someFunction(){
.
.
.
var getResult = await sendRequest()... //need to catch it here 
.
.
}

#

const request = net.request(
            {
                method: type,
                url: url,
                headers: headers,
            });
        request.on('login', (authInfo, callback) => {
            
        });

        request.on('response', (response) => {
             response.on('error', (error) => {
                resolve({status: false});
            })
            response.on('data', (chunk) => {
                
                
            })
            response.on('end', () => {
            })
        });

#

This is how sendRequest function looks like mainly

final barn Jun 8, 2023, 8:10 PM

#

request.on('error'

runic swan Jun 8, 2023, 8:36 PM

#

thanks!

#

@final barn

runic swan Jun 9, 2023, 12:20 PM

#

@final barn

#

    at new NodeError (node:internal/errors:399:5)
    at Socket._writeGeneric (node:net:920:8)
    at Socket._write (node:net:942:8)
    at doWrite (node:internal/streams/writable:411:12)
    at clearBuffer (node:internal/streams/writable:572:7)
    at Writable.uncork (node:internal/streams/writable:351:7)
    at ClientRequest._flushOutput (node:_http_outgoing:1133:10)
    at ClientRequest._flush (node:_http_outgoing:1102:22)
    at onSocketNT (node:_http_client:906:9)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {
  code: 'ERR_SOCKET_CLOSED'```

#

this is error im not catching

#

with this

#

do you know why?

final barn Jun 9, 2023, 12:21 PM

#

no

runic swan Jun 9, 2023, 1:12 PM

#

final barn no

how can i catch ERR_SOCKET_CLOSE

#

do you have any idea? @final barn

#

request.on('error' doesnt handle it

final barn Jun 9, 2023, 1:16 PM

#

you can try other events https://www.electronjs.org/docs/latest/api/client-request#instance-events

Class: ClientRequest | Electron

Make HTTP/HTTPS requests.

runic swan Jun 9, 2023, 1:35 PM

#

ty

ashen steeple Jun 9, 2023, 4:14 PM

#

You need to use reject(error) in the error case to if you want to be able to try await catch something that you converted into a promise

runic swan Jun 10, 2023, 4:03 PM

#

ashen steeple You need to use reject(error) in the error case to if you want to be able to try...

im doing that just some errors are not appearing

#

such as err_socket_close

ashen steeple Jun 11, 2023, 8:06 AM

#

Ok. Because in on "error" you have a resolve instead of a reject in your code

runic swan Jun 13, 2023, 5:27 PM

#

ashen steeple Ok. Because in on "error" you have a resolve instead of a reject in your code

Does it matter? I'm returning either way something

#

im catching that on the other side on await

ashen steeple Jun 13, 2023, 6:56 PM

#

Only if you want to catch that with try catch

#Unable to catch errors