-
-
Notifications
You must be signed in to change notification settings - Fork 271
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
Avo issues with logger gem #3560
Comments
Thanks for reporting this @aldent95. We'll have a look and add a fix. |
This issue has been marked as stale because there was no activity for the past 15 days. |
Hi @aldent95 I wasn't able to reproduce it, it's working as expected on my side. May be related with this logger issue. Could you please open a rails console on that project and try to run Let me know the output of it. Also please include a reproduction repository since I wasn't able to reproduce it following the described steps, it doesn't raise that error on my local environment. |
This issue has been marked as stale because there was no activity for the past 15 days. |
Closing this because there was no activity for the past 15 days. Feel free to reopen if new information pops up ✌️ |
Describe the bug
Avo prevents a Rails application from being launched with logger gem version 1.6.3 or higher
Reproduction repository for the bug
Can be reproduced from a fresh rails app made using the following rails new command (Change the directory for your system)
rails _8.0.1_ new D:/Dev/Test --javascript=importmap --skip --database=sqlite3
Steps to use in the reproduction repository
Uncaught exception: no implicit conversion of Pathname into String
errorExpected behavior & Actual behavior
Expected: Rails should run fine
Actual:
System configuration
Avo version: 3.14.5^
Rails version: 8.0.0^
Ruby version: 3.3.1
License type:
Are you using Avo monkey patches, overriding views or view components?
Screenshots or screen recordings
N/A
Additional context
This may be a problem with logger itself, but I think it's an Avo issue because no other gem I use seems to have the issue
Impact
Urgency
The text was updated successfully, but these errors were encountered: