-
Notifications
You must be signed in to change notification settings - Fork 125
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
Update activesupport #394
Update activesupport #394
Conversation
Given this solution, what is your advice on how to run erb_lint in the context of a bundle with rails 7.0 and concurrent-ruby 1.3.5? |
If you add logger to your Gemfile, then concurrent-ruby will be able to find it in your bundle. |
It's not concurrent-ruby that needs to find it, it's activesupport. Even when logger is in the bundle, there's no code that requires it when running
|
Oh right, the solution for now is to lock concurrent-ruby to 1.3.4 or to run FWIW the changes from this PR here didn't change the gem at all, just the development environment for the gem. To fix this, we could either depend on activesupport It's just that Active Support 7.0 is broken with concurrent-ruby 1.3.5:
|
Oh I forgot one workaround you might be able to use: $ bundle binstub erb_lint
$ ruby -pi -e 'print %(require "logger"\n) if /Gem\.bin_path/' -- bin/erb_lint
$ # replace all occurrences of `bundle exec erb_lint` with `bin/erb_lint` Not great, but until you can upgrade, that's probably the simplest. |
Thanks @etiennebarrie, I will try that workaround. |
After merging #392, CI failed on ruby-head because
logger
is no longer part of the standard library.It could be added to Bundler, but instead I upgraded activesupport so that we are testing with Active Support 8.0. But it's incompatible with Ruby 3.1 so I also tweaked the CI scripts to use an older version there.