Improve logging so that it would show why the stream is failing despite status 200 from proxy

[samip5]

As tittle, it seems often I get an 200 status from proxy but playback doesn't start despite it, and I have no way of knowing what's the issue.

It should return the upstream aka YouTube's reponses status code and message at least if it's having issues.

[samip5]

@FireMasterK I was looking into possibly logging the response body, but it seems I'm really out of my depth here with Rust as all of the ways I have tried results in it not compiling. :(

Pretty much all of the ways would consume the resp on line 347 in main.rs: let resp = CLIENT.execute(request).await;
Which of course makes everything else not really happy. Some guidance would be much appreciated.

This my StackOverflow question about this: https://stackoverflow.com/questions/78466365/rust-trying-to-include-response-body-to-my-response-with-reqwest-and-actix-web?noredirect=1#comment138333145_78466365

[jollySleeper]

Hey @samip5, I was also thinking of adding logs but the LLM's suggested me not to as this project should aim to squeeze out as much high performance as possible and logging will add overhead to I/O and CPU.
Only way of debugging your issue is by self-hosting and fiddling with proxy's code to figure out the issue.