invalid encoding name: unicode

[vohmar]

Every time deploy is done this error is caught by errbit

invalid encoding name: unicode

https://errbit.internet.ee/apps/5bcf2b35d9d1af5a21961be2/problems/5c051556d9d1af253512a4ad

Backtrace
--
/home/registry/registry/shared/bundle/ruby/2.4.0/gems/activerecord-4.2.11/lib/active_record/connection_adapters/postgresql_adapter.rb:671 → set_client_encoding /home/registry/registry/shared/bundle/ruby/2.4.0/gems/activerecord-4.2.11/lib/active_record/connection_adapters/postgresql_adapter.rb:671 → configure_connection /home/registry/registry/shared/bundle/ruby/2.4.0/gems/activerecord-4.2.11/lib/active_record/connection_adapters/postgresql_adapter.rb:277 → reconnect! /home/registry/registry/shared/bundle/ruby/2.4.0/gems/activerecord-4.2.11/lib/active_record/connection_adapters/abstract_adapter.rb:340 → verify! /home/registry/registry/shared/bundle/ruby/2.4.0/gems/activerecord-4.2.11/lib/active_record/connection_adapters/abstract/connection_pool.rb:456 → block in checkout_and_verify

[maciej-szlosarczyk]

I made a comment on the Errbit issue earlier. Root cause is the fact that the connection is dropped, and the error message is misleading.

https://bitbucket.org/ged/ruby-pg/issues/267/misleading-error-invalid-encoding-name

Fixed in later version of postgres adapter, which we cannot use yet:

https://bitbucket.org/ged/ruby-pg/commits/a7f98864a7d6

---

I am not certain if mina should drop a connection like that, and this is probably the fix.

[artur-intech]

Maybe it's also worth updating mina first...

[teadur]

Updating mina means rewriting the config for it, so its not trival, but doable if we don't have any other option.

[vohmar]

pushing this way back in the dev pipeline then