Command key should be fully quantified.
This improves the Hystrix dashboard reporting information. 

If you have two fns with the same name in different namespaces,
their command key will be the same. This messes up any monitoring using the Hystrix dashboard.
It is also confusing that circuit breakers are only shown by their command key. 
Namespaces provide more useful information in reporting.
Removing unused Legend component latent. Removed from html templates/css
Bugfix to HystrixBadRequestException handling - logs were spuriously getting generated when HystrixBadRequestExceptions got thrown
Merge pull request #182 from chrisgray/bug/remove_latent

Removing unused Legend component latent. Removed from html templates/css
Merge pull request #183 from mattrjacobs/bad-request-exception-handling

Bugfix to HystrixBadRequestException handling
BugFix: queue() BadRequestException Handling on Cached Response

The HystrixBadRequestException was being thrown directly instead of via the returned Future when a cached response was retrieved.

See included unit test for details.
Merge pull request #181 from josephwilk/clojure-hystrix-command-names

[hystrix-contrib/hystrix-clj] Making Command keys quantified by namespaces.
Merge pull request #184 from benjchristensen/queue-cached-future-exception

BugFix: queue() BadRequestException Handling on Cached Response
BugFix: Observable.observeOn Scheduler Lost RequestContext

The HystrixRequestContext was not being copied across Rx Scheduler boundaries. It now is by using a HystrixContextScheduler similar to HystrixContextCallable/HystrixContextRunnable.
Merge pull request #185 from benjchristensen/request-context

BugFix: Observable.observeOn Scheduler Lost RequestContext
rxjava-core:[0.14,0.15)
[Gradle Release Plugin] - pre tag commit:  '1.3.6'.
[Gradle Release Plugin] - new version commit:  '1.3.7-SNAPSHOT'.
Version 1.3.6
Version 1.3.6
BugFix: ConcurrencyStrategy.wrapCallable was not being used for reactive event-loop threads.

The Rx Scheduler now correctly has state transferred to it with ConcurrencyStrategy.wrapCallable.

Note that if the Rx sequence ever migrates to another thread (such as using observeOn) it is up to the user to deal with this as Hystrix loses control of the flow at that point.

This change does ensure though that the initial threads the callbacks are performed on has the expected thread context.

The design of this code is not very elegant and uses a workaround similar to posting variables on a stack before a method uses them. I have used this approach because I do not want to add a 'wrapFunc2' method to the ConcurrencyStrategy as the use of Func2 is just an implementation detail internally and the users of the library should not have to replicate the effort for both Callable and Func2. Thus the internal code is a little odd but the public API is untouched.
BugFix: Race condition between run() and timeout

This uses compareAndSet to synchronize timeout vs run() completion logic when there is a race.

I have not been able to to replicate the issue reported at https://github.com/Netflix/Hystrix/issues/188 but I can see how the existing code is vulnerable to a race condition. This theoretically should fix it. All unit tests pass for existing functionality. All my attempts to create a unit test to reveal the issue failed.
Protecting against timeout race-condition for error handling.
Merge pull request #190 from benjchristensen/concurrencyStrategyWithRx

BugFix: ConcurrencyStrategy.wrapCallable was not being used on callbacks
Merge pull request #189 from benjchristensen/issue-188

BugFix: Race condition between run() and timeout