aboutsummaryrefslogtreecommitdiffstats
path: root/activesupport/test/notifications_test.rb
Commit message (Collapse)AuthorAgeFilesLines
* Rename Rails::Subscriber to Rails::LogSubscriberPrem Sichanugrist2010-02-161-3/+3
|
* Remove instrument! and require thread from AS::Notifications.José Valim2010-02-041-17/+1
|
* deOMGifying Railties, Active Support, and Action PackMikel Lindsaar2010-01-311-3/+3
|
* Default to sync instrumentation.José Valim2010-01-211-17/+1
|
* Add ActionDispatch::Notifications middleware.José Valim2010-01-171-0/+16
|
* Yield the payload notifications for further modification (like adding the ↵José Valim2010-01-151-2/+2
| | | | result).
* Add instrument! to notifications which adds the result to the payload.José Valim2010-01-141-1/+11
|
* Do not send notifications when instrumentation raise an error.José Valim2010-01-131-7/+4
|
* instrumenter should be accessible from ActiveSupport::Notifications.José Valim2010-01-061-7/+10
|
* Expose Instrumenter id in Notifications.José Valim2010-01-041-0/+4
|
* Remove ActionView inline logging to ActiveSupport::Notifications and create ↵José Valim2009-12-261-12/+10
| | | | ActionController::Base#log_event, so everything can be logged within one listener. Also expose log_process_action as a hook for different modules to include their own information during the action processing. This allow ActiveRecord to hook and any other ORM. Finally, this commit changes 'Processing' and 'Rendering' in logs to 'Processed' and 'Rendered' because at the point it's logged, everying already happened.
* Notifications: synchronous fanout queue pushes events to subscribers rather ↵Jeremy Kemper2009-11-291-0/+10
| | | | than having them concurrently pull
* Notifications: extract central Notifier, cordon off the internal Fanout ↵Jeremy Kemper2009-11-281-158/+112
| | | | implementation, and segregate instrumentation concerns
* Expose a simple Queue#wait to block until all notifications are drainedJeremy Kemper2009-11-281-1/+1
|
* Revert "Create SyncListener. Since they do not rely on Thread, they can be ↵Jeremy Kemper2009-11-281-16/+1
| | | | | | | | used on Google App Engine." Take a step back on this API direction. This reverts commit 8104f65c3225453d13307c3c2733c2a8f99e491a.
* Create SyncListener. Since they do not rely on Thread, they can be used on ↵José Valim2009-11-231-1/+16
| | | | | | Google App Engine. Signed-off-by: Yehuda Katz <wycats@Yehuda-Katz.local>
* Notifications: queue.drained? for testability in place of brittle sleepsJeremy Kemper2009-11-131-10/+14
|
* Fix duration check for longer sleepJeremy Kemper2009-11-131-1/+1
|
* CI: slow down brittle notifications testsJeremy Kemper2009-11-131-9/+10
|
* Change Event#thread_id to #transaction_id. Defaults to one "transaction" per ↵Yehuda Katz2009-10-281-0/+20
| | | | thread but you can explicitly declare the start of a new one. This makes it possible for each request to have it own id.
* AS::Notifications.subscribe blocks are now yielded the arguments to pass to ↵Yehuda Katz2009-10-271-4/+14
| | | | AS::Notifications::Event.new
* Some optimizations on AS::Notifications. This does not change the ↵Yehuda Katz2009-10-271-11/+18
| | | | public-facing API.
* Renamed Orchestra to Notifications once again [#3321 state:resolved]José Valim2009-10-151-0/+164
|
* Revert "Rename Orchestra to Notifications [#3321 state:resolved]"José Valim2009-10-151-161/+0
| | | | This reverts commit 8cbf825425dc8ad3770881ea4e100b9023c69ce2.
* Rename Orchestra to Notifications [#3321 state:resolved]Joshua Peek2009-10-141-0/+161