day_planner 0.1.0.pre32 → 0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 1ff45c10b5a4bb3819d567e8eef31cb7fd1632c4
-  data.tar.gz: e5d25dd3784cb0f95b2dc57000ca80390ca8ae09
+  metadata.gz: 6e271590157c68f68b21acaa7d4ba3847b60d6e0
+  data.tar.gz: 7e94325e55aca06a0d99055faf83304c326cb8eb
 SHA512:
-  metadata.gz: 60e0a44cee133a468dfa694798b1ef4e5b4783e670c7f0b4ca73269bc75f2f04f5860ddd526396452405b96642f105f2401d2aad73dd1446ecefc1c6433ded70
-  data.tar.gz: d622a3a1b158cd50896bd89938c0e5ef4eba03045657f5905a857288a9141251d4e4c4b0690b8bad083dbdd4ce6827364ec66f4225de46f3d92a5179c8a5c123
+  metadata.gz: 69b1689fc1993c8e6dddd98fc38da980cb790f0b55de4f7216744dd3788dd4180f00c64d9fa04eae00ca0410ab4250e1ae7d6d142d9fc099585ae136d0d9a43f
+  data.tar.gz: e4b7effe0a70f8eec035ca0a773653275ee3854c6c11a8aafcad3f02df88190d56e29a55735d05d35a62a56325b0a859f288d62ca97726418a0d3d9660f0da7e

data/README.md

@@ -30,7 +30,7 @@ This file will be read in and its tasks will be added to the schedule automatica
 
 The tasks in the schedule will each be performed on startup and then thereafter according to their stated intervals.
 
-I'm not doing a whole damn ton to protect you from tasks that throw errors, but there is a begin/rescue/end up in there at some point. I definitely am not protecting you from a process that just won't end or anything like that. Remember that your interval is more or less the minimum possible time between instances of the task being performed, as it does not spawn a new thread for each task. (That seemed to cause problems with Heroku.) Setting a shorter interval will help, as it will endeavor to catch up to the schedule if it falls behind but will never execute tasks between its check intervals. Setting the check interval too short could end up blocking your application's main thread, though, particularly if your tasks end up running long.
+I'm not doing a whole damn ton to protect you from tasks that throw errors, but there is a begin/rescue/end up in there at some point. I definitely am not protecting you from a process that just won't end or anything like that. Remember that your interval is more or less the minimum possible time between instances of the task being performed, as it does not spawn a new thread for each task. (That seemed to cause problems with Heroku.) Setting a shorter interval will help, as it will endeavor to catch up to the schedule, by running a task as soon as after half its specified interval if it's fallen behind, but will never execute tasks between the master scheduler thread's check intervals. Setting the check interval too short could end up blocking your application's main thread, though, particularly if your tasks end up running long.
 
 ### Options
 
@@ -80,7 +80,7 @@ If you'd like to log your tasks, go for it. Add logging thusly:
     rails generate day_planner:log
     rake db:migrate
 
-This just adds an extra table entitled 'day_planner_log'. As long as the table's there, it'll log each task execution, as well as every instance in which DayPlanner activates.
+This just adds an extra table entitled 'day_planner_log'. As long as the table's there, it'll log each task execution, as well as every instance in which DayPlanner activates. In addition, it logs each tasks's 'deviation' -- how late it ran, as compared to its previous run -- and the task's 'cumulative deviation', based on previous deviation values for that task's name. This makes it possible for the anxious taskmaster to track the task's runs over time and monitor "catchup" instances.
 
 It may be worth considering clearing the log on every launch. You can add such instruction to your schedule file:
 

data/app/models/day_planner/task.rb

@@ -14,7 +14,7 @@ module DayPlanner
 			end
 
 			fields = {}
-			fields[:name] = options.delete(:name) if options[:name]
+			fields[:name] = options.delete(:name).to_s if options[:name]
 			fields[:interval] = options.delete(:every).to_i if options[:every]
 
 			task = DayPlanner::Task.create(fields)

data/lib/day_planner/version.rb

@@ -2,7 +2,7 @@ module DayPlanner
 	MAJOR = 0
 	MINOR = 1
 	TINY  = 0
-	PRE   = "pre32"
+	PRE   = nil
 	BUILD = nil
 
   VERSION = [MAJOR, MINOR, TINY, PRE, BUILD].compact.join(".")

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: day_planner
 version: !ruby/object:Gem::Version
-  version: 0.1.0.pre32
+  version: 0.1.0
 platform: ruby
 authors:
 - Damon Siefert
@@ -106,9 +106,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: 1.9.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>'
+  - - '>='
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubyforge_project: 
 rubygems_version: 2.0.14