Nathan Sizemore
Nathan Sizemore
It's not the types, but the actual pipe '|'. The left one gets highlighted, but the right one does not. If there are less than 3 params, both get highlighted.
Ah yes, removing that from example4 and example1 did the trick.
I'm using 2 16:9s. I doubt it's the intended placement behavior, which is why I reported it as a bug.
@matthijskooijman Understandable. If I get enough free time in the coming weeks, I'll get it taken care of and send a PR
This causes false error types to show up in logs, through the logging facade tracing is built upon. So in the instance of the remote link being established, an error...
This also would bring in the same span type as websocket remote. It uses info, this uses error.
> > This shows itself when logging blocks are built around the log facade directly > > can you elaborate more? didn't get it 😅 Sure. If you look at...
> > because rumqttd uses that error span, that shows up as error type on our end > > wdym by _error type_ ? The log type comes in as...
> > Maybe it is just when instrument is called with it, this is the only spot it happens. > > Might be issue with instrument then? 👀 We should...
Ah yeah, it is critical for our end to know as fast as possible when a client is no longer connected.