Michael Gee

> I'm not sure if there's a valid reason to use `id: false` besides creating a join table? Not if the Rails developers control the database schema. But, sometimes we...

My changes allowed query_reviewer to run in production and be invisible to all but an admin user. Feel free to break my use case, though. I got what I needed...

Development and discussion was moved to https://github.com/rspec-given/rspec-given, given Jim is no longer with us.

> I'm not sure if there's a valid reason to use `id: false` besides creating a join table? Not if the Rails developers control the database schema. But, sometimes we...

@movitto no worries. We ended up writing a bunch of classes with HappyMapper. It's kinda tedious, and HappyMapper doesn't know about the xsd, so we have to validate everything we...

> We are using older versions of rack and can’t update to latest version. That is certainly unfortunate. Please understand that your particular application cannot dictate how past versions of...

Here's a hacky workaround I've been using: in `config/production.rb` ```ruby RemoteSyslogLogger::Logger = ActiveSupport::Logger ``` It works because `Logger` being used within the `RemoteSyslogLogger` module here: https://github.com/papertrail/remote_syslog_logger/blob/506bba071f09082106aacd6d3cc3e17423d99dac/lib/remote_syslog_logger.rb#L9 `RemoteSyslogLogger::Logger` is typically undefined...

> We ended up being able to switch back to the Rails standard logger sending to STDOUT, and having the container do the remote syslogging. I'm interested in switching to...

@illegalnumbers did you get this issue worked out?

If the repro doesn’t fail anymore, is it time to close this?