veza icon indicating copy to clipboard operation
veza copied to clipboard

bug: MessageError: Failed to process message during connection, calling disconnect: Unknown type received: 1 [UnknownType]

Open kakarot-dev opened this issue 3 years ago • 2 comments

Is there an existing issue for this?

  • [X] I have searched the existing issues

Description of the bug

If i leave the connection on from some time, it throws this error and shuts the whole process down

Steps To Reproduce

Expected behavior

No errors

Screenshots

image

Additional context

No response

kakarot-dev avatar Feb 11 '22 01:02 kakarot-dev

found any fixes? I received the exact error, But after a lot of debugging, I got more logs. Veza uses binarytf for serializing and deserializing and searching the below error on binarytf repo shows an old closed issue with a pr. I guess it's still around and not fixed? It's some kind of Buffer overflow. https://github.com/binarytf/binarytf/pull/10 I found the source in binarytf, not sure how to fix it.

parse error @1:0: 4 (not well-formed (invalid token)).
[ 1080205 ]: | Tue, 19 Jul 2022 00:52:08 | INFO | Manager.log | Worker Disconnected: worker1080220
[ 1080205 ]: | Tue, 19 Jul 2022 00:52:08 | ERROR | Manager.log | Error: Socket has been disconnected.
    at ServerSocket.disconnect (/home/Sofi/node_modules/veza/dist/lib/ServerSocket.js:80:33)
    at ServerSocket._onClose (/home/Sofi/node_modules/veza/dist/lib/ServerSocket.js:115:14)
    at Socket.emit (node:events:527:28)
    at Socket.emit (node:domain:475:12)
    at TCP.<anonymous> (node:net:709:12)

legendhimself avatar Jul 19 '22 02:07 legendhimself

Sorry I did not. I degraded my node version as that was the only thing I could do

kakarot-dev avatar Jul 19 '22 17:07 kakarot-dev