You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever call events arrive, we get a log message like this:
DEBUG [2021-05-06T22:22:26.606378555Z] Failed to parse content of [$tFsRCPRjzbsPMfBBDPwtygFdo0PPa2rd67yKWZJdFYU m.call.hangup unsupported content type m.call.hangup (message)] (%!s(MISSING)): %!v(MISSING)
It looks like this is just because the Call events types aren't recognised as Message events in GuessClass - looks like the structures are all there so I guess the types just need to be added here?
Also I'm not sure where the %s(MISSING) stuff is coming from in the log line. For unknown event types, maybe something like, "Unknown message type /: not parsing" would be a better debug log?
The text was updated successfully, but these errors were encountered:
Whenever call events arrive, we get a log message like this:
It looks like this is just because the Call events types aren't recognised as Message events in
GuessClass
- looks like the structures are all there so I guess the types just need to be added here?Also I'm not sure where the %s(MISSING) stuff is coming from in the log line. For unknown event types, maybe something like, "Unknown message type /: not parsing" would be a better debug log?
The text was updated successfully, but these errors were encountered: