Fix CI failure #40
Merged
Fix CI failure #40
+20
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
require 'rails/all' fails with the following error on Rails 6 > uninitialized constant ActiveSupport::LoggerThreadSafeLevel::Logger (NameError)
Or bundler bundles sqlite 3 verson 2.x that is not supported by old version of Active Record.
Because we'll run bundle update soon later.
Rails 6 + concurrent-ruby 1.3.5+ causes uninitialized constant ActiveSupport::LoggerThreadSafeLevel::Logger (NameError)
In order to enable [[ command
spring 4.3.0 on old version of Rails (e.g. 6.x) causes `initialize': Rails::Application is abstract, you cannot instantiate it directly. (RuntimeError)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I tried to send a PR to this repo and noticed that the CI is currently not passing for various reasons.
So, here's a patch that fixes all CI problems and makes the CI green again. For the "reasons", please take a look at the commits.