-
-
Notifications
You must be signed in to change notification settings - Fork 124
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
No such middleware to insert before: Rails::Rack::Logger #199
Comments
There was a community supplied PR submitted to switch to Rackup, want to give it a try with the new Rails Semantic Logger v4.14.0? |
I've had the same error with v4.14.0 |
we also get this error with: |
No longer seeing this issue after updating to the latest version from the Rails |
Same issue here with rails 7.1.3.2 |
We are seeing this against a large monolith using Rails 6.1.7.6. |
We are also seeing this issue:
|
I face this issue during upgrade from ruby 2.7 to 3.0 without any changes to gem versions rails 6.1.7 I think it not related to semantic logger itself |
I just did a first time install using ruby 3.3.6, rails 7.1.5, rails_semantic_logger 4.17.0 and semantic_logger 4.16.1. With some Googling I realized this was due to a conflict with the gem Silencer, which initialized with:
Removing this cleared up the error and logging worked as expected. |
Environment
Provide at least:
branch: '7-1-stable'
)Note:
Expected Behavior
RSpec should be able to run without unhandled errors coming rails_semantic_logger.
Actual Behavior
Error occurs immediately when attempting to run
rspec
after updating Rails Semantic Logger to 4.13.0 and Rails from v7.0 to v7.1.Stack Trace:
Pull Request
The text was updated successfully, but these errors were encountered: