Fredrik Enestad

:cry: That is very sad indeed!

Have you checked via kubectl that the pods in this state are actually deleted, and not in some non running state, such as Completed or Evicted?

I can confirm that if you upgrade to 1.2.0 without also upgrading the CRDs, your charts will end up in a state where they continuously upgrade even when there is...

This would be very useful for debugging http2 frames, especially when the service is behind a proxy, and you need to debug frames sent between the backend and the proxy

Noted that if I change the order of these filters it works as expected: ```rust let layer = tracing_subscriber::fmt::layer() .with_filter(filter::LevelFilter::DEBUG) .with_filter(SomeFilter); ``` And it also works as expected(?) if I...

I should also mention that if I remove `.with_filter(SomeFilter)` it also works as expected :thinking:

This actually seems to have to do with layers that have max_level_hint set to `None` (like `SomeFilter` in the previous example). The same issue occurs with this code, here the...

Hey @guswynn, sorry for making this issue more complicated than it needed to be. The `maybe_layer` code is more close to the real app than the `MyLayer` code, but maybe...

@markmeeus did you ever resolve this? and if so, what was the solution?

I've noticed that I have the same problem when running a cluster of 2 nodes, when I run 3 nodes the `:begin_handoff` and `:resolve_conflict` callbacks are called as expected.