ruby-clock 0.8.0.rc3 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7e8d972bb2c2468f53d943f233e4e799df71a449b6f7b8c00a1ddbea33c54c92
-  data.tar.gz: fc97259d0575bd220f79dd25206128001eece56ec51eda06d95f28d718b65080
+  metadata.gz: bb7709e5cb45330de5b30adb906cc15e847207894a2ad71b3afd706ea0235f09
+  data.tar.gz: 9ab66e406ada9646d83f28806c07018641953b7b56f8824b49e14b3bd2ad2b7c
 SHA512:
-  metadata.gz: 6dcf79cbebb137a9f04e920b8d6ff0f910bd61536e3e666297217aef8d9942c656fca0d67d794c753ab42a9e035be364bcf3d3b6e465058ebfe7e8683fa94fea
-  data.tar.gz: a3ca20e788af53d77d5526aaacb3b7ff4b07e8852e7586fe181e1681985b32b5bce3a9f0a305507be335dfeee7399567a6cd31afe8262b6e0b84db9cd2d9a75a
+  metadata.gz: d14858bb6c936e07e66527c9f670d68e236d56ccce407da9c5472334748a3b3f07012f82ff827fb314557b318a555a0e50ff9914b36330fe9cbd7c271da76532
+  data.tar.gz: '033369b93174cdba782d21fa150f63f521bf058d9ef6a654fbb54fd53e2b529f753350b5e086aa2b7e5df2cd0647cf9f932aceb6aaeabba892727dfb978ed1a8'

data/.gitignore

@@ -1,3 +1,4 @@
+Gemfile.lock
 /.bundle/
 /.yardoc
 /_yardoc/

data/CHANGELOG.md

@@ -1,13 +1,7 @@
-## 0.8.0 RC3
+## 1.0.0
 
 * make terrapin and posix-spawn gems optional
-
-## 0.8.0 RC2
-
 * fix detection of Rails constant, for non-rails apps
-
-## 0.8.0 RC1
-
 * automatically wrap jobs with rails reloader
 * ability to run rake tasks
 * ability to run shell commands

data/README.md

@@ -12,8 +12,8 @@ ruby-clock does.
 
 Jobs are all run in their own parallel threads within the same process.
 
-The clock process will respond to signals INT (^c at the command line) and
-TERM (signal sent by environments such as Heroku and other PaaS's when shutting down).
+The clock process will respond to signals `INT` (<kbd>^c</kbd> at the command line) and
+`TERM` (signal sent by environments such as Heroku and other PaaS's when shutting down).
 In both cases, the clock will stop running jobs and give existing jobs 29 seconds
 to stop before killing them.
 You can change this number with `RUBY_CLOCK_SHUTDOWN_WAIT_SECONDS` in the environment.
@@ -75,7 +75,22 @@ To get smarter database connection management (such as in the case of a database
 and maybe other benefits) and code reloading in dev (app code, not the code in Clockfile itself),
 jobs are automatically wrapped in the
 [rails app reloader](https://guides.rubyonrails.org/threading_and_code_execution.html).
+This [may incur a performance impact for certain jobs](https://github.com/rails/rails/issues/43504),
+I'm still exploring this.
 
+#### ActiveRecord Query Cache
+
+You may wish to
+[turn off the ActiveRecord Query Cache](https://code.jjb.cc/turning-off-activerecord-query-cache-to-improve-memory-consumption-in-background-jobs)
+for your jobs. You can do so with the around trigger:
+
+```ruby
+def schedule.around_trigger(job)
+  ActiveRecord::Base.uncached do
+    yield
+  end
+end
+```
 
 ### Non-Rails
 
@@ -165,6 +180,22 @@ schedule.every '1 day' do
 end
 ```
 
+#### shutdown behavior
+
+Because of [this](https://stackoverflow.com/questions/69653842/),
+if a shell job is running during shutdown, shutdown behavior seems to be changed
+for _all_ running jobs - they no longer are allowed to finish within the timeout period.
+Everything exits immediately.
+
+Until this is figured out, if you are concerned about jobs exiting inelegantly,
+you may want to run your shell jobs in their own separate clock process.
+
+```
+bundle exec rails runner bin/clock clocks/main_jobs.rb
+bundle exec rails runner bin/clock clocks/shell_jobs.rb
+```
+
+
 ### Rake tasks
 
 You can run tasks from within the persistent runtime of ruby-clock, without

data/example-app/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: ..
   specs:
-    ruby-clock (0.8.0.rc2)
+    ruby-clock (0.8.0.rc3)
       method_source
       rufus-scheduler (~> 3.8)
 

data/example-app/README.md

@@ -5,5 +5,5 @@ To run:
 
 ```
 bundle
-bundle exe clock
+bundle exec clock
 ```

data/lib/ruby-clock/version.rb

@@ -1,3 +1,3 @@
 module RubyClock
-  VERSION = "0.8.0.rc3"
+  VERSION = "1.0.0"
 end

data/lib/ruby-clock.rb

@@ -42,7 +42,7 @@ module RubyClock
       puts <<~MESSAGE
         Because this is not a rails application, we do not know how to load your
         rake tasks. You can do this yourself at the top of your Clockfile if you want
-        to run rake tasks from ruby-cron.
+        to run rake tasks from ruby-clock.
       MESSAGE
     end
   end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ruby-clock
 version: !ruby/object:Gem::Version
-  version: 0.8.0.rc3
+  version: 1.0.0
 platform: ruby
 authors:
 - John Bachir
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-10-20 00:00:00.000000000 Z
+date: 2022-04-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rufus-scheduler
@@ -49,7 +49,6 @@ files:
 - ".gitignore"
 - CHANGELOG.md
 - Gemfile
-- Gemfile.lock
 - LICENSE.txt
 - README.md
 - Rakefile
@@ -82,9 +81,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: 2.3.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubygems_version: 3.2.22
 signing_key:

data/Gemfile.lock

@@ -1,33 +0,0 @@
-PATH
-  remote: .
-  specs:
-    ruby-clock (0.8.0.rc2)
-      method_source
-      rufus-scheduler (~> 3.8)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    concurrent-ruby (1.1.9)
-    et-orbi (1.2.5)
-      tzinfo
-    fugit (1.5.2)
-      et-orbi (~> 1.1, >= 1.1.8)
-      raabro (~> 1.4)
-    method_source (1.0.0)
-    raabro (1.4.0)
-    rake (12.3.3)
-    rufus-scheduler (3.8.0)
-      fugit (~> 1.1, >= 1.1.6)
-    tzinfo (2.0.4)
-      concurrent-ruby (~> 1.0)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  rake (~> 12.0)
-  ruby-clock!
-
-BUNDLED WITH
-   2.2.23