ruby-clock 0.8.0.rc1 → 0.8.0.rc2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 77de35a13a23a83386d574ebc2ff0e71777f65b3612a9a444afd4f9ea69286bf
-  data.tar.gz: 95cec8207417b487dfb81fb20b9cc8147bd90200efb009cc56a8c023773979bf
+  metadata.gz: 2ec6ebc2ef5793e7d114920402b20ed5129e1f60a78cb444d208e45def25a36b
+  data.tar.gz: 3935724aaa45567dd2e769274f76fc1b5a3785f155d4885764a25635a8bf6c96
 SHA512:
-  metadata.gz: a5585b7af51d706ffcbac3b88881c9b9c189dbc80e08867feea9ecef690dfd04957593504415bffde2c2022f69c1afdb0b30472f2466baa6bfc0dfad1264855d
-  data.tar.gz: b1a9aa07dfcaaf28f8d953c88f9ccc467ac199376dce674bff1b3fac7aef3a01416dd9638a40d5fd28ae23932d56e1f56b74888fdb485c4dce3dd9fa6ed579aa
+  metadata.gz: cf58749b267218114e3ad235fa64d0c7e21cecc13c75f6a655b63cf16f056dcc174e6cd724be74c3a5c39087eec808e03d72829674cff52d85f0f831340efeb3
+  data.tar.gz: 04eefdc557205145fad64889dec7f7dcf6af4ead08dcc8795af58be4fffc2a54d97bb261048478c98aab58be30124e47f1d35c5115976cdd4119b95903e9b5ce

data/CHANGELOG.md

@@ -1,10 +1,14 @@
+## 0.8.0 RC2
+
+* fix detection of Rails constant, for non-rails apps
+
 ## 0.8.0 RC1
 
-* fixed rare error when calculating job identifier
-* nicer shutdown logging, indicating when shutdown process begins and ends
+* automatically wrap jobs with rails reloader
 * ability to run rake tasks
 * ability to run shell commands
-* automatically wrap jobs with rails reloader
+* nicer shutdown logging, indicating when shutdown process begins and ends
+* fix approach for error fallbacks when when calculating job identifier (probably never encountered)
 
 ## 0.7.0
 

data/Gemfile.lock

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

data/README.md

@@ -108,6 +108,14 @@ 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.
 
+#### Observing logs
+
+Because STDOUT does not flush until a certain amount of data has gone into it,
+you might not immediately see the ruby-clock startup message or job output if
+viewing logs in a deployed environment such as Heroku where the logs are redirected
+to another process or file. To change this behavior and have logs flush immediately,
+add `$stdout.sync = true` to the top of your Clockfile.
+
 
 ## More Config and Capabilities
 

data/example-app/.gitattributes

@@ -0,0 +1 @@
+Clockfile linguist-language=Ruby

data/example-app/Clockfile

@@ -0,0 +1,3 @@
+schedule.every('2 seconds') do
+  puts "hello from a ruby-clock job"
+end

data/example-app/Gemfile

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+gem 'ruby-clock', path: '../'

data/example-app/Gemfile.lock

@@ -0,0 +1,37 @@
+PATH
+  remote: ..
+  specs:
+    ruby-clock (0.8.0.rc1)
+      method_source
+      posix-spawn (~> 0.3.15)
+      rufus-scheduler (~> 3.8)
+      terrapin (~> 0.6)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    climate_control (0.2.0)
+    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)
+    posix-spawn (0.3.15)
+    raabro (1.4.0)
+    rufus-scheduler (3.8.0)
+      fugit (~> 1.1, >= 1.1.6)
+    terrapin (0.6.0)
+      climate_control (>= 0.0.3, < 1.0)
+    tzinfo (2.0.4)
+      concurrent-ruby (~> 1.0)
+
+PLATFORMS
+  arm64-darwin-20
+
+DEPENDENCIES
+  ruby-clock!
+
+BUNDLED WITH
+   2.2.28

data/example-app/README.md

@@ -0,0 +1,9 @@
+This is a bare-bones example non-rails app to
+help with dev and also as an example for users.
+
+To run:
+
+```
+bundle
+bundle exe clock
+```

data/exe/clock

@@ -25,7 +25,7 @@ schedule.pause
 
 load ARGV[0] || 'Clockfile'
 
-if ::Rails
+if defined?(::Rails)
   schedule.instance_eval do
     @old_around_trigger = method :around_trigger
     def around_trigger(job)

data/lib/ruby-clock/version.rb

@@ -1,3 +1,3 @@
 module RubyClock
-  VERSION = "0.8.0.rc1"
+  VERSION = "0.8.0.rc2"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ruby-clock
 version: !ruby/object:Gem::Version
-  version: 0.8.0.rc1
+  version: 0.8.0.rc2
 platform: ruby
 authors:
 - John Bachir
-autorequire: 
+autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-09-18 00:00:00.000000000 Z
+date: 2021-10-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rufus-scheduler
@@ -66,7 +66,7 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: 0.3.15
-description: 
+description:
 email:
 - j@jjb.cc
 executables:
@@ -83,6 +83,11 @@ files:
 - Rakefile
 - bin/console
 - bin/setup
+- example-app/.gitattributes
+- example-app/Clockfile
+- example-app/Gemfile
+- example-app/Gemfile.lock
+- example-app/README.md
 - exe/clock
 - lib/ruby-clock.rb
 - lib/ruby-clock/version.rb
@@ -94,7 +99,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
@@ -109,8 +114,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: 1.3.1
 requirements: []
-rubygems_version: 3.2.23
-signing_key: 
+rubygems_version: 3.2.22
+signing_key:
 specification_version: 4
 summary: A "clock" process for invoking ruby code within a persistent runtime
 test_files: []