Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Apr 14, 2015
  1. Version 1.2.0

    authored
    Job name becomes optional, and options hash can take in place of job name.
    Kind contributors revised README.
  2. Merge branch 'ankane_fix'

    authored
  3. Apply default job name

    authored
  4. @ankane

    More intuitive behavior for unnamed jobs

    ankane authored committed
  5. Merge pull request #146 from pmukerji/patch-1

    authored
    Clarify README note about tasks being skipped
Commits on Apr 2, 2015
  1. @pmukerji
Commits on Jan 28, 2015
  1. Merge pull request #139 from dlackty/patch-1

    authored
    Test against Ruby 2.2 and use bundler cache
  2. @dlackty

    Fix test failure for Ruby 2.2

    dlackty authored
Commits on Jan 25, 2015
  1. @dlackty
Commits on Jan 18, 2015
Commits on Nov 24, 2014
  1. Merge pull request #137 from recursive-madman/patch-1

    authored
    Update README.md
  2. @recursive-madman

    Update README.md

    recursive-madman authored
    Being placed in bin/ doesn't make something a binary.
Commits on Nov 19, 2014
  1. Version 1.1.0

    authored
    Accept #135 to fix drifting start time.
    As a side effect, sleep_timeout < 1 is disallowed.
  2. Remove .ruby-version

    authored
    There are no need to restrict developer's ruby version.
    CI will detect problems.
  3. Warn if sleep_timeout < 1

    authored
  4. Wait until the next second

    authored
Commits on Nov 14, 2014
  1. @brianhempel

    Default sleep_timeout to 0.5 seconds to not skip any seconds

    brianhempel authored
    Because sleep means “sleep at least this amount”, and because there is some processing between sleep calls (even though it’s trivial), with a sleep_timeout of 1 second it is possible for the manager to pass over a second without ticking. (E.g. tick at 10:00:00.999 and tick at 10:00:02.001, but nothing during 10:00:01).
    
    The previous commit ensures that Clockwork won’t let job start times drift later and later *as long as* the manager ticks once during every second.
    
    Changing the sleep_timeout to 0.5 seconds make sure the manager ticks at least once during every second.
    
    With this change and the previous commit, Clockwork *by default* will not allow jobs to start running later and later.
  2. @brianhempel

    Don’t let job start time drift later and later

    brianhempel authored
    Because jobs were supposed to wait at least their period length before running again, their actual start time would slip further and further from their expected start time. (With the default sleep_timeout of 1 second, we observed a drift of about 0.6 seconds per period. On average, each hourly job ran 1 hour + 0.6 seconds later than the last.)
    
    For an hourly job, if the last job ran at 10:00:00.5 it should be safe to run again at 11:00:00.1. By pretending the last job actually ran at the beginning of the second (10:00:00.0) we are able to trigger the new job on time.
Commits on Nov 5, 2014
  1. Merge pull request #133 from allcentury/ar-RMupdate

    authored
    Update on Production Content
  2. @allcentury
  3. @allcentury
Commits on Oct 5, 2014
  1. @robisenberg

    Version 1.0.2

    robisenberg authored
  2. @robisenberg

    Merge pull request #129 from robisenberg/fix_duplicate_database_event…

    robisenberg authored
    …s_from_firing_for_models_without_name_method
    
    Fix duplicate database events from firing for models without #name method
  3. @robisenberg

    Refactor ActiveRecordFake to use composition rather than inheritance

    robisenberg authored
     * the previous implementation meant that each subclass had to have
       various things defined in the subclass (e.g. instance variables)
       that are needed to provide features implemented in the parent. This
       new implementation removes the need for this.
  4. @robisenberg
  5. @robisenberg

    Bugfix: duplicate database events fire for models without name method

    robisenberg authored
    DatabaseEvents::Event#name_has_changed? was incorrectly returning true
    if the model object didn't respond to `#name`. This was a purely logical
    error: the name must be considered *not* to have changed if the model's
    `#name` method isn't implemented otherwise every sync will result in the
    event being recreated (and therefore re-run).
Commits on Oct 1, 2014
  1. Remove custom numeric overrides

    authored
    Use those from ActiveSupport.
    This fixes #122.
Commits on Sep 16, 2014
  1. @robisenberg

    Version 1.0.1

    robisenberg authored
  2. @robisenberg

    Merge pull request #124 from robisenberg/fix_database_events_readme_m…

    robisenberg authored
    …istake
    
    Bugfix: README incorrectly requires old database events manager file
  3. @robisenberg
Commits on Sep 2, 2014
  1. @robisenberg

    Version 1.0.0

    robisenberg authored
  2. @robisenberg

    Merge pull request #114 from robisenberg/database_events_refactor

    robisenberg authored
    Database events: major refactor
  3. @robisenberg
Something went wrong with that request. Please try again.