"Error: Could not encode" when set mode "development"

Question

"Error: Could not encode" when set mode "development"

qiulang opened this issue 2 years ago · comments

I notice I only have dashboard and servers menu

I think this is because start my nodejs using "NODE_ENV=production node index.js" so I set mode code specifically in code

instrument(io, {
  auth: {
     ...
  },
  mode: "development"
});

But then server crash with error

Error: Could not encode
 at _encode (/home/express/node_modules/notepack.io/lib/encode.js:256:13)
 at _encode (/home/express/node_modules/notepack.io/lib/encode.js:162:19)
 at _encode (/home/express/node_modules/notepack.io/lib/encode.js:162:19)
 at _encode (/home/express/node_modules/notepack.io/lib/encode.js:246:17)
 at _encode (/home/express/node_modules/notepack.io/lib/encode.js:162:19)
 at Object.encode (/home/express/node_modules/notepack.io/lib/encode.js:261:41)
 at RedisAdapter.broadcast (/home/express/node_modules/socket.io-redis/dist/index.js:313:33)
 at BroadcastOperator.emit (/home/express/node_modules/socket.io/dist/broadcast-operator.js:109:22)
 at Namespace.emit (/home/express/node_modules/socket.io/dist/namespace.js:170:73)
 at Socket.<anonymous> (/home/express/node_modules/@socket.io/admin-ui/dist/index.js:284:36)

I searched this error and found someone else also hit this error

https://bestofvue.com/repo/socketio-socket-io-admin-ui-vuejs-web-sockets (at "7. Error serialising sockets with session stores")

qiulang · Answer 1 · Tue Jul 19 2022 15:54:23 GMT+0800 (China Standard Time)

I saw this issue #7 was closed at 0.1.2 but I am using 0.4.0 (and "socket.io-redis": "^6.1.1") and still hit it.

Michael R. Garfinkel · Answer 2 · Sat Aug 20 2022 05:02:23 GMT+0800 (China Standard Time)

+1 seeing it myself as well

Michael R. Garfinkel · Answer 3 · Sat Aug 20 2022 05:03:12 GMT+0800 (China Standard Time)

Here is my stacktrace (similar to above)

Aryaman Behera · Answer 4 · Thu Oct 06 2022 05:57:49 GMT+0800 (China Standard Time)

I'm encountering the same issue, only with mode set as "development", otherwise it works great.
Is there any workaround available for the same @qiulang @darrachequesne ?

Damien Arrachequesne · Answer 5 · Thu Oct 06 2022 14:43:30 GMT+0800 (China Standard Time)

I think I have found the culprit, this should be fixed by 6d58a75.

I'll publish a new version later today.

Aryaman Behera · Answer 6 · Thu Oct 06 2022 16:24:20 GMT+0800 (China Standard Time)

I think I have found the culprit, this should be fixed by 6d58a75.

I'll publish a new version later today.

That's awesome! Waiting for it

Damien Arrachequesne · Answer 7 · Fri Oct 07 2022 16:03:02 GMT+0800 (China Standard Time)

Released in 0.5.1. Thanks for your patience 👍

qiulang · Answer 8 · Mon Oct 10 2022 17:27:42 GMT+0800 (China Standard Time)

@darrachequesne I have verified 0.5.1 worked and I would like turn it into feature request: is it possible to make mode setting a runtime setting, so I can turn it on and off when I need ?

I understand the development mode will be a burden to https://admin.socket.io/ but we will host the Admin UI server ourselves so a runtime setting is more appropriate.

qiulang · Answer 9 · Mon Oct 10 2022 18:49:35 GMT+0800 (China Standard Time)

@darrachequesne 0.5.1 also fixed the issue I raised here darrachequesne/notepack#29