You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 1.10 and 1.11 the Context returned by ServerStreamTracer.filterContext was attached when streamClosed was invoked. As of 1.12 (and continuing through 1.14) this no longer seems to be the case. It appears this was undocumented behavior and relying on it was my mistake.
That said, I think it would be nice if ServerStreamTracer methods were guaranteed to be invoked with the filtered Context attached. Either way, it would be helpful to have the Javadoc for filterContext specify whether or not the filtered Context is attached when other ServerStreamTracer methods are invoked.
The text was updated successfully, but these errors were encountered:
streamClosed() was never meant to be run under the context. I looked back at 1.11 code but was unable to confirm that it was the case. It needs to be clarified in the javadoc and a regression test to enforce it.
In 1.10 and 1.11 the
Context
returned byServerStreamTracer.filterContext
was attached whenstreamClosed
was invoked. As of 1.12 (and continuing through 1.14) this no longer seems to be the case. It appears this was undocumented behavior and relying on it was my mistake.That said, I think it would be nice if
ServerStreamTracer
methods were guaranteed to be invoked with the filteredContext
attached. Either way, it would be helpful to have the Javadoc forfilterContext
specify whether or not the filteredContext
is attached when otherServerStreamTracer
methods are invoked.The text was updated successfully, but these errors were encountered: