1. 15 Feb, 2016 2 commits
    • Import the autoconfig for server properties · 86d51528
      Dave Syer authored
      Otherwise there can be duplicate beans with the same type and different
      names, becasue the autoconfig does not (for some reason) use
      @EnableConfigurationProperties to create the ServerProperties bean.
      
      It isn't an issue until someone writes some autoconfig that itself
      imports the ZuulConfiguration (i.e. regular concious users of
      @EnableZuulServer do not see any problems and hence no tests fail
      here or in integration projects).
      
      Fixes gh-821
    • Improved query string handling to present empty keys correctly · 67258446
      Nicolas Byl authored
      I.e. show empty "foo" as foo (not foo=)
      
      Fixes gh-825
  2. 12 Feb, 2016 4 commits
  3. 11 Feb, 2016 3 commits
  4. 09 Feb, 2016 3 commits
  5. 05 Feb, 2016 5 commits
  6. 04 Feb, 2016 3 commits
  7. 03 Feb, 2016 3 commits
  8. 02 Feb, 2016 2 commits
  9. 01 Feb, 2016 5 commits
    • Merge pull request #802 from herder/patch-1 · 199c740c
      Spencer Gibb authored
      Fix typo: zule-core -> zuul-core.
    • Fix broken zuul tests. · 63896485
      Spencer Gibb authored
    • Merge pull request #800 from brharrington/spectator-issue-264 · 3611edd1
      Spencer Gibb authored
      * spectator-issue-264:
        fix registration bug in SpectatorMetricServices
    • fix registration bug in SpectatorMetricServices · 63b0c8c6
      Brian Harrington authored
      The primary change is to fix a memory leak reported in
      Netflix/spectator#264. Each time a gauge was updated it
      was creating a new registration and because the map holds
      a strong reference these would never get collected.
      Further, the aggregate value created by the multiple
      registrations was not correct.
      
      In addition I added some test cases around the various
      inputs and checked that the results were reflected as
      expected in the registry. I noticed the timer values
      had a unit of milliseconds, but it isn't immediately
      clear if the reported value can ever less than 1.0. The
      conversion to long is now delayed until after converting
      to nanoseconds so duration values less than 1.0 will now
      work instead of just recording 0.
      
      For the histogram I changed to just using a cast to `long`
      to avoid boxing to a `Double`. As an FYI for the future,
      there is a DoubleDistributionSummary we have experimented
      with in spectator-ext-sandbox that might be more appropriate
      for this use-case.
  10. 31 Jan, 2016 2 commits
  11. 29 Jan, 2016 2 commits
  12. 28 Jan, 2016 2 commits
  13. 27 Jan, 2016 4 commits