You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Rails 6.0, for the example that threw the exception above, we get this line in the log:
2021-01-19 13:33:28.549474 D [87304:puma threadpool 004] (7.359ms) ActiveRecord -- {:sql=>"SELECT COUNT(*) FROM "schools" WHERE "schools"."status" = $1 AND ("schools"."computacenter_change" IN ($2, $3) OR "schools"."computacenter_reference" IS NULL)", :binds=>{:status=>"open", :computacenter_change=>["new", "amended"]}}
After some further research, it looks like this will be addressed in Rails if and when PR 41068 makes it into a future release. Hopefully this won't be too long
Environment
Ruby Version 2.7.2p137
Rails Version 6.1.1
Semantic Logger Version 4.7.4
Rails Semantic Logger Version 4.4.6
Other Application/framework names and versions (e.g. Puma, etc.) puma. Gemfile is here
Relevant part of the Rails configuration in our repo: config/initializers/semantic_logger.rb
Full Stack Trace:
Expected Behavior
On Rails 6.0, for the example that threw the exception above, we get this line in the log:
2021-01-19 13:33:28.549474 D [87304:puma threadpool 004] (7.359ms) ActiveRecord -- {:sql=>"SELECT COUNT(*) FROM "schools" WHERE "schools"."status" = $1 AND ("schools"."computacenter_change" IN ($2, $3) OR "schools"."computacenter_reference" IS NULL)", :binds=>{:status=>"open", :computacenter_change=>["new", "amended"]}}
Actual Behavior
On Rails 6.1, we get the exception above.
Pull Request
I haven't identified a fix yet, but have added a test case which reliably reproduces the issue: https://github.com/rocketjob/rails_semantic_logger/pull/120
The text was updated successfully, but these errors were encountered: