magicseth
magicseth2y ago

WebSocket closed unexpectedly.

I'm seeing some internal errors in the browser console, that don't show up in the web dashboard WebSocket closed unexpectedly with code 1011: InternalServerError: Your request couldn't be completed. Try again later. ws.onclose @ web_socket_manager.ts:221 19:00:05.806
6 Replies
lee
lee2y ago
hi! that's not supposed to happen. can you share your deployment url (from settings in the dashboard) so i can search for the error on our side?
magicseth
magicsethOP2y ago
dmed
lee
lee2y ago
thanks! we identified the issue. it appears we have a problem if you try to store null terminator characters \u0000 inside strings. we may have difficulty supporting these strings in the short term, so we're considering improving the error message. can you describe your use-case? 🙏
magicseth
magicsethOP2y ago
Unintentional! Just stress testing your system apparently! The issue went away for me, but I'm not sure why it would have been sending them before?
lee
lee2y ago
@sujayakar is on the case and we should be able to support this soon. 🥳 the issue should be fixed now, so you may now commence storing null terminators in strings. have fun 🙂
Gorka Cesium
Gorka Cesium14mo ago
I'm getting the same error nevermind, i was trying to pass to useQuery a string instead of using the api

Did you find this page helpful?