Thank you for pursuing this and keeping at this!
The error message reminds me of a bugfix where the (number of) parameters given to a callback changed with some version of AnyEvent::WebSocket, which I think I fixed already, but it seems I haven't even published the change on Github yet. Update: Now the change has been pushed.
In any case this sounds like a bug in my codebase to me, so I'll have to find out what callback is called at that place and whether my latest changes fix that. Having internal errors vanish silently is infuriating to me, and my codebase certainly shouldn't gobble up such errors.
I've seen those other warnings, but I'm not familiar enough with Websockets to know what an empty message should be, and whether undef would be allowed there.
In reply to Re^5: Problem with WWW::Mechanize::Chrome
by Corion
in thread Problem with WWW::Mechanize::Chrome
by ivartr
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |