ruby-clock 0.3.0 → 0.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6c02c6cf2aa2de399ec607078946ec4b83cacfbb54cc4a4e27e6180b790e7b07
-  data.tar.gz: e0c6d50e81133d3e28e93c72f5e1f5033707fae3e812acf24188ff8377f5cf4f
+  metadata.gz: 2681c0a4279cd09c1c12b8495148b426f3af51ed8620615441ad013f2e21e40a
+  data.tar.gz: db0aea19c254edf9007dd9d1f34a8d1d9616e864972187f1345857ae6ad4f4db
 SHA512:
-  metadata.gz: 3da2592ecc97fb84401ff49b68f7841e069d2d38e3638a8a00ea501a257bd7b89fcde9fb48ac48b0197ca1c4e2e2dc572eea79f1910421ef2f5db1e8939c6c6c
-  data.tar.gz: 26cfcc6d5bd17035712c964c7a2325794260a8218ba223dc45a72b552d7dcd2615af22882f4af25a2a5737e4ea27ec5f1c374a8bdde82130e3c48b213b09eba2
+  metadata.gz: 1461d0c51349a1d635dc85dfc54a691753b48be4fcba2b687257d415d74fb8ced8b9fe15471f7940212bfd1ebf82ed8df2ccb93519f769c5c4034c0cc748a762
+  data.tar.gz: c0120a55ef27d303c66d64f895d664f359cf0edc568fe7ddef6515e62079e99a3767b93ef1f75e83d6ca9971bec08b16fb51f34f8172d67e621045027acd3739

data/CHANGELOG.md

@@ -0,0 +1,4 @@
+## 0.7.0
+
+* ability to specify the name of the file with job definitions, e.g. `bundle exec clock clocks/MyClockfile`
+* ability to specify the amount of time ruby-clock will wait before forcing threads to shut down

data/Gemfile.lock

@@ -1,21 +1,23 @@
 PATH
   remote: .
   specs:
-    ruby-clock (0.3.0)
-      rufus-scheduler (~> 3.7.0)
+    ruby-clock (0.6.0)
+      method_source
+      rufus-scheduler (~> 3.8)
 
 GEM
   remote: https://rubygems.org/
   specs:
-    concurrent-ruby (1.1.7)
+    concurrent-ruby (1.1.9)
     et-orbi (1.2.4)
       tzinfo
-    fugit (1.4.1)
+    fugit (1.5.0)
       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.7.0)
+    rufus-scheduler (3.8.0)
       fugit (~> 1.1, >= 1.1.6)
     tzinfo (2.0.4)
       concurrent-ruby (~> 1.0)

data/README.md

@@ -16,6 +16,7 @@ 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).
 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.
 
 ## Installation
 
@@ -55,11 +56,20 @@ To start your clock process:
 
     bundle exec clock
 
+To use a file other than Clockfile for job definitions, specify it.
+This will ignore Clockfile and only read jobs from clocks/MyClockfile:
+
+    bundle exec clock clocks/MyClockfile
+
 ### Rails
 
+Install the `clock` binstub and commit to your repo.
+
+    bundle binstubs ruby-clock
+
 To run your clock process in your app's environment:
 
-    bundle exec rails runner clock
+    bundle exec rails runner bin/clock
 
 ### Non-Rails
 
@@ -76,9 +86,23 @@ schedule.every('5 minutes') do
 Add this line to your Procfile
 
 ```
-clock: bundle exec rails runer clock
+clock: bundle exec rails runner bin/clock
+```
+
+You might have a main clock for general scheduled jobs, and then standalone ones
+if your system has something where you want to monitor and adjust resources
+for that work more precisely. Here, maybe the main clock needs a 2GB instance,
+and the others each need 1GB all to themselves:
+
+```
+clock: bundle exec rails runner bin/clock
+thing_checker: bundle exec rails runner bin/clock clocks/thing_checker.rb
+thing_reporter: bundle exec rails runner bin/clock clocks/thing_reporter.rb
 ```
 
+Because of this feature, do I regret using "Clockfile" instead of, say, "clock.rb"? Maybe.
+
+
 ## More Config and Capabilities
 
 ### Error Handling
@@ -98,6 +122,63 @@ You can define before, after, and around callbacks which will run for all jobs.
 Read [the rufus-scheduler documentation](https://github.com/jmettraux/rufus-scheduler/#callbacks)
 to learn how to do this. Where the documentation references `s`, you should use `schedule`.
 
+### Job Identifier
+
+ruby-clock adds the `identifier` method to `Rufus::Scheduler::Job`. This method will return the job's
+[name](https://github.com/jmettraux/rufus-scheduler/#name--string) if one was given.
+If a name is not given, the last non-comment code line in the job's block
+will be used instead. If for some reason an error is encountered while calculating this, the next
+fallback is the line number of the job in Clockfile.
+
+Some examples of jobs and their identifiers:
+
+```ruby
+schedule.every '1 second', name: 'my job' do |variable|
+  Foo.bar
+end
+# => my job
+
+schedule.every '1 day' do |variable|
+  daily_things = Foo.setup_daily
+  daily_things.process
+  # TODO: figure out best time of day
+end
+# => daily_things.process
+
+# n.b. ruby-clock isn't yet smart enough to remove trailing comments
+schedule.every '1 week' do |variable|
+  weekly_things = Foo.setup_weekly
+  weekly_things.process # does this work???!1~
+end
+# => weekly_things.process # does this work???!1~
+```
+
+This can be used for keeping track of job behavior in logs or a
+stats tracker. For example:
+
+```ruby
+def schedule.on_post_trigger(job, trigger_time)
+  duration = Time.now-trigger_time.to_t
+  StatsTracker.value('Clock: Job Execution Time', duration.round(2))
+  StatsTracker.value("Clock: Job #{job.identifier} Execution Time", duration.round(2))
+  StatsTracker.increment('Clock: Job Executions')
+end
+
+schedule.every '10 seconds', name: 'thread stats' do
+  thread_usage = Hash.new(0)
+  schedule.work_threads(:active).each do |t|
+    thread_usage[t[:rufus_scheduler_job].identifier] += 1
+  end
+  thread_usage.each do |job, count|
+    StatsTracker.value("Clock: Job #{job} Active Threads", count)
+  end
+
+  StatsTracker.value("Clock: Active Threads", schedule.work_threads(:active).size)
+  StatsTracker.value("Clock: Vacant Threads", schedule.work_threads(:vacant).size)
+  StatsTracker.value("Clock: DB Pool Size", ActiveRecord::Base.connection_pool.connections.size)
+end
+```
+
 ### other rufus-scheduler Options
 
 All rufus-scheduler options are set to defaults. The `schedule` variable
@@ -107,6 +188,14 @@ so anything you can do on this instance, you can do in your Clockfile.
 Perhaps in the future ruby-clock will add some easier specific configuration
 capabilities for some things. Let me know if you have a request!
 
+## Syntax highlighting for Clockfile
+
+To tell github and maybe other systems to syntax highlight Clockfile, put this in a .gitattributes file:
+
+```gitattributes
+Clockfile linguist-language=Ruby
+```
+
 
 ## License
 

data/exe/clock

@@ -1,10 +1,24 @@
 #!/usr/bin/env ruby
 
 require 'ruby-clock'
+require 'method_source'
+
+class Rufus::Scheduler::Job
+  def identifier
+    @identifier ||= begin
+      name || handler.source.split("\n").reject(&:empty?).grep_v(/#.*/)[-2].strip
+    rescue
+      source_location.join('-')
+    rescue
+      'error-calculating-job-identifier'
+    end
+  end
+end
+
 include RubyClock
 
 listen_to_signals
 
-load 'Clockfile'
+load ARGV[0] || 'Clockfile'
 
 run_jobs

data/lib/ruby-clock/version.rb

@@ -1,3 +1,3 @@
 module RubyClock
-  VERSION = "0.3.0"
+  VERSION = "0.7.0"
 end

data/lib/ruby-clock.rb

@@ -3,14 +3,22 @@ require 'rufus-scheduler'
 
 module RubyClock
   def shutdown
-    puts "Shutting down 🐈️ 👋"
-    puts Rufus::Scheduler.singleton.shutdown(wait: 29)
-    exit
+    puts "Shutting down ruby-clock 🐈️ 👋"
+    Rufus::Scheduler.singleton.shutdown(wait: ENV['RUBY_CLOCK_SHUTDOWN_WAIT_SECONDS']&.to_i || 29)
   end
 
   def listen_to_signals
-    Signal.trap('INT') { shutdown }
-    Signal.trap('TERM') { shutdown }
+    signals = %w[INT TERM]
+    signals.each do |signal|
+      old_handler = Signal.trap(signal) do
+        shutdown
+        if old_handler.respond_to?(:call)
+          old_handler.call
+        else
+          exit
+        end
+      end
+    end
   end
 
   def schedule
@@ -18,6 +26,7 @@ module RubyClock
   end
 
   def run_jobs
+    puts "Starting ruby-clock with #{schedule.jobs.size} jobs"
     Rufus::Scheduler.singleton.join
   end
 end

data/ruby-clock.gemspec

@@ -29,5 +29,6 @@ Gem::Specification.new do |spec|
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.require_paths = ["lib"]
 
-  spec.add_dependency "rufus-scheduler", '~> 3.7.0'
+  spec.add_dependency "rufus-scheduler", '~> 3.8'
+  spec.add_dependency "method_source"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ruby-clock
 version: !ruby/object:Gem::Version
-  version: 0.3.0
+  version: 0.7.0
 platform: ruby
 authors:
 - John Bachir
-autorequire: 
+autorequire:
 bindir: exe
 cert_chain: []
-date: 2020-12-31 00:00:00.000000000 Z
+date: 2021-09-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rufus-scheduler
@@ -16,15 +16,29 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 3.7.0
+        version: '3.8'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 3.7.0
-description: 
+        version: '3.8'
+- !ruby/object:Gem::Dependency
+  name: method_source
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+description:
 email:
 - j@jjb.cc
 executables:
@@ -33,6 +47,7 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".gitignore"
+- CHANGELOG.md
 - Gemfile
 - Gemfile.lock
 - LICENSE.txt
@@ -50,7 +65,7 @@ licenses:
 metadata:
   homepage_uri: https://github.com/jjb/ruby-clock
   source_code_uri: https://github.com/jjb/ruby-clock
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -65,8 +80,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.2
-signing_key: 
+rubygems_version: 3.2.23
+signing_key:
 specification_version: 4
 summary: A "clock" process for invoking ruby code within a persistent runtime
 test_files: []