Max Inden

Addressing these two comments from the two of you: > > A sender SHOULD send a STREAM_DATA_BLOCKED frame (type=0x15) when it wishes to send data but is unable to do...

@artemlive First of all **thank** you very much for this very detailed bug report! Before digging further into this, two questions: 1. Is there a particular reason why you specify...

This is quite confusing and sounds like a bug. Are you able to reproduce this with a minimal config? It is difficult for me to reconstruct your exact environment for...

> I will update to AlertManager 0.16.1 and see if it helps, however I don't see anything related to this in the Changelog. @steve-exley Yes, please try anything above and...

👋 https://github.com/mozilla/neqo/issues/2807 has been fixed. The latest Docker image should be up-to-date. Let me know in case you are still facing any issues.

> Turns out we cannot make the initialization conditioned on `cfg(test)`, because before a test uses one of the logging macros, the log init won't happen and there will no...

Why is that? The `cfg(test)` should be true in that case, no?

I think we need to get to the root of this before merging. Especially since this might interfere with Firefox's logging setup.

> @claude says > > ``` > The issue is that #[cfg(test)] doesn't cross crate boundaries in macros. > > The solution: Use #[cfg(debug_assertions)] instead of #[cfg(any(test, feature = "bench"))]....

Regarding #3025: wow, didn't expect such an impact. Regarding the suggested changes, Firefox already implements a more aggressive version of it: > debug! and trace! logs will not appear in...