Swanand Mulay

Hey, entering runtime context shall fix this, you can verify by using `fix-recv-timeout` branch ```toml rumqttc = { default-features = false, git = "https://github.com/bytebeamio/rumqtt", branch = "fix-recv-timeout" } ```

Use boundary mode, i.e. -b flag to only match the whole text and not any part of it!

Boundaryless mode is on by default for lemmeknow binary, that is why it identified the phone number, if you add `-b` flag to turn it off, you will see the...

Facing similar issue with rustls & native-tls: ```rust // this enables tokio-native-tls feature #[cfg(feature = "use-native-tls")] let connector = tls::native_tls_connector(&tls_config).await?; // enables tokio-rustls-native-certs & tokio-rustls-webpki-roots #[cfg(feature = "use-rustls")] let connector...

it was set to `error_span!` because otherwise tracing won't capture / show additional fields with error log normally ( unless we set verbosity to `-vvv` ) see #510

> This shows itself when logging blocks are built around the log facade directly > can you elaborate more? didn't get it :sweat_smile:

> because rumqttd uses that error span, that shows up as error type on our end > wdym by _error type_ ? btw, `error_span!` is used in other places, like...

> 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 investigate it...

> After checking, this does effect all other logs. I just didn't notice immediately because I forgot I muted all of routing because of this reason as weill > oh,...

> Can I get a comment on this PR? > hey, sorry about the delay but i'm currently caught up with other work, so don't have enough bandwidth for this...