according to issue #612:
> When 2 or more customized HystrixConcurrencyStrategy are registered (e.g SleuthHystrixConcurrencyStrategy and SecurityContextConcurrencyStrategy) depending on the order of registration the overrides from SecurityContextConcurrencyStrategy might get ignored.
I think the override and delegation should be made all methods of HystrixConcurrencyStrategy otherwise the delegation will possibly be incomplete.
fixes#612
without this change we allways force Feign to use Hystrix
with this change you need to pass the `feign.hystrix.enabled=true` flag to turn it on
fixes#627
without this change there's no way to alter the exception message that gets attached as a tag to the span
with this change you can register your own ErrorParser bean to alter that behaviour
fixes#576
without this change we're always setting values for headers regardless of the fact whether they have already been set.
with this change we're only setting headers if there was no any previous value of the header
fixes#586
with this change we're injecting a list of adjusters instead of a single one. That way you don't have to create a composite version
of adjusters.
fixes#595
without this change any update on a span in custom exception resolver where ignored cause the span got detached in TraceFilter instead of it getting closed
with this change we're adding an error tag if it was missing and we're also marking the span for closure by TraceFilter
fixes#585
without this change when dealing with Zuul, it's TraceFilter that is closing a span on an error
with this change, we're allowing the PostZuulFilter to close that span and TraceFilter doesn't interfere
fixes#563
without this change when an executor implementation was a final class or had a final method - the application wouldn't start or would produce NPE at startup.
with this change we have a custom bean post processor that wraps an aspect manualy either via a JDK Proxy when a class is final or a method is final or creates a CGLIB proxy if that's possible.
fixes#550
without this change when an executor implementation was a final class or had a final method - the application wouldn't start or would produce NPE at startup.
with this change we have a custom bean post processor that wraps an aspect manualy either via a JDK Proxy when a class is final or a method is final or creates a CGLIB proxy if that's possible.
fixes#550
without this change when user adds a callback then it's not wrapped in a trace representation, thus when executed in a separate thread, it's then missing all the tracing information
with this change we're wrapping the future in our representation that passes the tracing information around
fixes#546
without this change when user adds a callback then it's not wrapped in a trace representation, thus when executed in a separate thread, it's then missing all the tracing information
with this change we're wrapping the future in our representation that passes the tracing information around
fixes#546
