You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing an error after updating the clockwork gem from 2.0.2 to 2.0.3:
app/vendor/bundle/ruby/2.5.0/gems/tzinfo-1.2.5/lib/tzinfo/zoneinfo_data_source.rb:208:in `load_timezone_info': Invalid identifier (TZInfo::InvalidTimezoneIdentifier)
from /app/vendor/bundle/ruby/2.5.0/gems/tzinfo-1.2.5/lib/tzinfo/timezone.rb:92:in `get'
from /app/vendor/bundle/ruby/2.5.0/gems/clockwork-2.0.3/lib/clockwork/event.rb:20:in `convert_timezone'
from /app/vendor/bundle/ruby/2.5.0/gems/clockwork-2.0.3/lib/clockwork/event.rb:24:in `run_now?'
from /app/vendor/bundle/ruby/2.5.0/gems/clockwork-2.0.3/lib/clockwork/manager.rb:163:in `block in events_to_run'
from /app/vendor/bundle/ruby/2.5.0/gems/clockwork-2.0.3/lib/clockwork/manager.rb:163:in `select'
from /app/vendor/bundle/ruby/2.5.0/gems/clockwork-2.0.3/lib/clockwork/manager.rb:163:in `events_to_run'
from /app/vendor/bundle/ruby/2.5.0/gems/clockwork-2.0.3/lib/clockwork/manager.rb:133:in `tick'
from /app/vendor/bundle/ruby/2.5.0/gems/clockwork-2.0.3/lib/clockwork/manager.rb:123:in `block (2 levels) in run_tick_loop'
from /app/vendor/bundle/ruby/2.5.0/gems/clockwork-2.0.3/lib/clockwork/manager.rb:121:in `synchronize'
from /app/vendor/bundle/ruby/2.5.0/gems/clockwork-2.0.3/lib/clockwork/manager.rb:121:in `block in run_tick_loop'
Tested with Ruby versions: 2.5.0 and 2.5.1
I can reproduce this locally (Ubuntu 16.04) running bundle exec clockwork config/clock.rb. This does not happen with version 2.0.2
The text was updated successfully, but these errors were encountered:
I am experiencing an error after updating the
clockwork
gem from 2.0.2 to 2.0.3:Tested with Ruby versions: 2.5.0 and 2.5.1
I can reproduce this locally (Ubuntu 16.04) running
bundle exec clockwork config/clock.rb
. This does not happen with version 2.0.2The text was updated successfully, but these errors were encountered: