Mateusz

I did hit the same issue with is strange because that worked for months inside the container fine. I don't think this is a bug inside cargo watch but some...

Sure, no problem! ``` docker info Client: Context: default Debug Mode: false Plugins: compose: Docker Compose (Docker Inc., 2.10.2) Server: Containers: 29 Running: 5 Paused: 0 Stopped: 24 Images: 297...

That strange, today it is working. Maybe a reboot fixed it :/

> My next project (hopefully) is to refactor the drivers so that the runtime and TLS features can be orthogonal, and part of that would include fixing this while improving...

> Huh, interesting find. I have disabled the URCs for those 3 that fails to distinguish the URC from response, but even with them enabled it should just discard them....

I don't have myself experience with nom yet, so I will be probably not a big help for that but I am not sure if that is the best approach,...

Wondering if the AtatResp trait could contain additional const that could help the parse qualify if the string readed does belong to it or not? This could be auto generated...

Not a solution but might be useful for other user as a workaround: ```rust async fn ingress_task( mut ingress: Ingress, ) { info!("modem ingress_task started"); loop { let buf =...

I am all for it, since I had the same idea but didn't yet had time to dive into the digest parser to find out how to do it.

> This is likely [rust-lang/rust#114518](https://github.com/rust-lang/rust/issues/114518), so I don't think anything can be done here about that. Oh yeah, that looks like it. Thanks for the link! I follow that up,...