Closed p-himik closed 1 year ago
I'm putting this here because I think this is related to the current issue, if not, happy to open a new one. The current situation isn't much better, printing this in console:
#error {:message "Invalid event", :data {:given :chsk/bad-package, :errors {:wrong-type
{:expected :vector
:actual {:type, :value :chsk/bad-package}}}}}
I can usually debug this by slowly filtering out stuff until I get to what's wrong, it would be useful if it stated what value was at fault?
@p-himik, @Folcon Apologies for such a long delay replying!
Thanks both for pinging about this, will be fixed in forthcoming v1.18 release 👍
Consider a scenario where a client cannot decode a message sent by a server. In this case, it results two messages in the JS console:
The warning message is created by this piece of code:
The issue is that in the problematic case,
cb-uuid
is set to thebad_data
. It's not nil so the error gets sent into the console and nowhere else.