Is there an existing issue for this?

• I have searched the existing issues

Description of the bug

Can't find the exact line this parse error is coming from. But this errors belongs to this code.
Veza uses binarytf to serialize and deserialize the data that it sends. Now the issue below comes while serialize/deserialize only.

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)

Steps To Reproduce

1. Create a server.
2. Spawn 12 child processes that connect to the bove server which is the parent process as well.
3. Heavy communication (for a few minutes-hours sometimes one of the child sends parse error @1:0: 4 (not well-formed (invalid token)). and gets disconnected and child process never reconnect)

Expected behavior

It should ignore the error and not disconnect. If it gets disconnected then worker having the retry quota available should be able to reconnect back

Screenshots

Additional context

No response