Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
1 task done
kakarot-dev opened this issue Feb 11, 2022 · 2 comments

Comments

@kakarot-dev
Copy link

Is there an existing issue for this?

  • 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 kakarot-dev changed the title bug: essageError: Failed to process message during connection, calling disconnect: Unknown type received: 1 [UnknownType] bug: MessageError: Failed to process message during connection, calling disconnect: Unknown type received: 1 [UnknownType] Feb 11, 2022
@legendhimself
Copy link

legendhimself commented Jul 19, 2022

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. binarytf/binarytf#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)

@kakarot-dev
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants