1. 15 8月, 2019 1 次提交
  2. 11 7月, 2017 1 次提交
  3. 09 7月, 2017 1 次提交
  4. 02 7月, 2017 1 次提交
  5. 01 7月, 2017 1 次提交
  6. 02 9月, 2016 1 次提交
  7. 07 8月, 2016 1 次提交
  8. 28 11月, 2015 1 次提交
    • T
      Subscribing to notifications while inside the said instrumented section. · ab3c4a40
      thedarkone 提交于
      The issue is that on the exit from Instrumenter#instrument section,
      an Evented listener will run into an error because its thread local
      (Thread.current[:_timestack]) has not been set up by the #start
      method (this obviously happens because the Evented listeners didn't
      exist at the time, since no subscribtion to that section was made yet).
      
      Note: support for subscribing to instrumented sections, while being
      inside those instrumented sections, might be removed in the future.
      
      Maybe fixes #21873.
      ab3c4a40
  9. 05 11月, 2015 1 次提交
  10. 19 9月, 2015 1 次提交
  11. 11 8月, 2015 1 次提交
  12. 02 6月, 2014 2 次提交
  13. 31 10月, 2013 1 次提交
  14. 29 10月, 2013 1 次提交
  15. 18 5月, 2013 1 次提交
  16. 14 12月, 2012 1 次提交
    • T
      Replace some global Hash usages with the new thread safe cache. · 45448a57
      thedarkone 提交于
      Summary of the changes:
       * Add thread_safe gem.
       * Use thread safe cache for digestor caching.
       * Replace manual synchronization with ThreadSafe::Cache in Relation::Delegation.
       * Replace @attribute_method_matchers_cache Hash with ThreadSafe::Cache.
       * Use TS::Cache to avoid the synchronisation overhead on listener retrieval.
       * Replace synchronisation with TS::Cache usage.
       * Use a preallocated array for performance/memory reasons.
       * Update the controllers cache to the new AS::Dependencies::ClassCache API.
         The original @controllers cache no longer makes much sense after @tenderlove's
         changes in 7b6bfe84 and f345e238.
       * Use TS::Cache in the connection pool to avoid locking overhead.
       * Use TS::Cache in ConnectionHandler.
      45448a57
  17. 12 8月, 2012 1 次提交
    • E
      Evented notifications take priority over Timed notifications · 6fe36ba5
      Eric Saxby 提交于
      In cases where a notification subscriber includes methods to support
      both Evented and Timed events, Evented should take priority over Timed.
      This allows subscribers to be backwards compatible (older Rails only
      allows Timed events) while defaulting to newer behavior.
      6fe36ba5
  18. 20 6月, 2012 3 次提交
  19. 22 3月, 2012 4 次提交
  20. 16 3月, 2012 1 次提交
  21. 27 4月, 2011 1 次提交
  22. 23 7月, 2010 1 次提交
  23. 20 7月, 2010 2 次提交
  24. 19 7月, 2010 3 次提交
  25. 18 7月, 2010 4 次提交
  26. 25 4月, 2010 1 次提交
  27. 18 3月, 2010 1 次提交
  28. 02 3月, 2010 1 次提交