Socket closes mid-generation

[transitive-bullshit]

Socket closes mid-generation

[roodkcab]

me too. and I added code below to output result already returned

        ws.on('close', () => {
          console.warn('WebSocket close')
          if (!isFulfilled) {
            isFulfilled = true
            resolve(result)
            return
          }
        })

I'm thinking it's may better to handle reconnect, since there's a message which type is 7 that allowReconnect, need to find out how bing handle this message on socket close

[roodkcab]

@IceCream0910 sorry, account being banned. maybe u can try to send {"type":6} every 15 seconds to keep connection alive.

[transitive-bullshit]

@semse I'm currently not able to test / reproduce since the shared Microsoft account a bunch of us were using got disabled.

[anhiao]

me too. and I added code below to output result already returned

        ws.on('close', () => {
          console.warn('WebSocket close')
          if (!isFulfilled) {
            isFulfilled = true
            resolve(result)
            return
          }
        })

I'm thinking it's may better to handle reconnect, since there's a message which type is 7 that allowReconnect, need to find out how bing handle this message on socket close

Thanks for your help, it is currently useful to solve the sometimes await unresponsive content

[alexandrius]

I noticed that {"type":6} is sent every 15 seconds or so. Maybe that's what keeps it alive. Can't test no more. I think I was banned.

[IceCream0910]

@roodkcab

I'm thinking it's may better to handle reconnect, since there's a message which type is 7 that allowReconnect, need to find out how bing handle this message on socket close

Did you find a solution? As you said, when the "{"type":7}" message, the socket connection is closed. Why does it disconnect even though no cleanup() was executed... I can't find a way to reconnect with my abilities.

[IceCream0910]

@IceCream0910 sorry, account being banned. maybe u can try to send {"type":6} every 15 seconds to keep connection alive.

Thanks, I sent type 6 messages and it works without stopping.

[binikingi]

@IceCream0910 Can you share the code?

[IceCream0910]

@IceCream0910 Can you share the code?
@binikingi

I'm not sure that my code is best solution, but I sends a type:6 request to websocket's 'on' event function. And when websocket is closed, stop interval using clearInterval.

ws.on("open", () => { 
           ws.send(`{"protocol":"json","version":1}${terminalChar}`); 
           reconnectInterval = setInterval(() => { 
             ws.send(`{"type":6}${terminalChar}`); 
           }, 10 * 1000); 
         });

...

[binikingi]

@IceCream0910 yup this works for me. thanks