-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 1.10.0 not compatible with ruby 2.2.6 #93
Comments
https://github.com/floraison/fugit/actions/runs/8087932820/job/22100915876 no 2.2.6, but no luck with 2.2.10 :-( |
@aunghtain Hello and thanks for the detailed report! I have trouble finding a Ruby 2.2.x or 2.2.6 to test directly, neither on GitHub Actions, neither for my development station (some kind of compile error). Could you please test this When we are successful, I will release a fugit 1.10.1. |
It still gives me the same error.
But if I move the include to a new line, it works fine.
Also, this works.
|
Well done! I will change and release 1.10.1. Thanks a lot! |
1.10.1 released https://rubygems.org/gems/fugit/versions/1.10.1 Please tell me if it works for you. Thanks! |
1.10.1 works! Thank you so much @jmettraux |
@aunghtain You're welcome! Well done! |
Issue description
The latest version (1.10.0) with ruby 2.2.6 gives the following error.
/usr/share/rvm/gems/ruby-2.2.6/gems/fugit-1.10.0/lib/fugit.rb:16:in
require': /usr/share/rvm/gems/ruby-2.2.6/gems/fugit-1.10.0/lib/fugit/cron.rb:323: syntax error, unexpected tIDENTIFIER, expecting '<' or ';' or '\n' (SyntaxError) class CronIterator include ::Enumerable ^ from /usr/share/rvm/gems/ruby-2.2.6/gems/fugit-1.10.0/lib/fugit.rb:16:in
<top (required)>'How to reproduce
I'm using it in rails with rufus-scheduler 3.6.0. After bundle install, I try to start rails console
I got the above error.
Error and error backtrace (if any)
Expected behaviour
Rails starts console without any issues.
Context
Please replace the content of this section with the output of the following commands:
Additional context
If I downgrade to 1.9.0, it works fine.
The text was updated successfully, but these errors were encountered: