@blaise ah ok, but yes I can see the same error message as such, but after revisiting the channel it seems to work fine. If that is what you mean, then this is very much an upstream bug.
I did a quick search in their issue tracker, but couldn't find anything specific yet.