|7eter l-|. l3oling

@JasonLunn I think most critically we need people with available time to work on the issues noted here: https://github.com/thiagopradi/octopus/issues/490#issuecomment-383667221 (three comments above this one)

This gem is struggling for maintenance with the current support load, so I vote to reduce the scope of supported Rubies and Railses with the next major release... Keeping latest...

@lunaru This is this the gem we are using on a hugely scaled application that is pushing the limits of PostgreSQL v9, having many tables with hundreds of millions of...

Many, if not all, of the features of Octopus may be part of Rails 6! https://github.com/rails/rails/pull/34052 I am not yet sure how we will bridge the gap from Rails 4.2...

I am have started seeing this as well on Rails 4.2.10 and Ruby 2.3.4.

I am running into a similar issue with `rake db:reset` in development mode, where we are trying to use Octopus to expose write to read only errors before they hit...

I am getting this error in production with Octopus 0.9.0, with Rails 4.2.7.1, on Ruby 2.2.6. Notably we do have spring installed on the production machine, and we shouldn't. (https://github.com/rails/spring#deployment)...

:+1:

+1

> I want all of the string columns to be stripped automatically. Doing things automatically seems aligned with a gem named `auto_*` 😉