Theo B
Theo B
Facing a similar problem here when trying to build a Docker image. Docker building process exits because `SECRET_KEY_BASE` is unavailable when `RUN bundle exec rake assets:precompile` starts. `The command '/bin/sh...
+1 Hayaku is a must have!
@wpolicarpo Yes, we do! Removing that I'm facing another error now. The relevant backtrace: ``` ActiveRecord::StatementInvalid: TinyTds::Error: Incorrect syntax near the keyword 'COLLATE'. .../activerecord-sqlserver-adapter-6.1.2.1/lib/active_record/connection_adapters/sqlserver/database_statements.rb:361:in `do' .../activerecord-sqlserver-adapter-6.1.2.1/lib/active_record/connection_adapters/sqlserver/database_statements.rb:361:in `raw_connection_do' .../activerecord-sqlserver-adapter-6.1.2.1/lib/active_record/connection_adapters/sqlserver/database_statements.rb:298:in `block in...
@aidanharan As observed by @wpolicarpo, seems like overriding the `configure_connection` method may affect something. If you wish to try to reproduce again with an initiliazer, our is more or less...
Receiving now the same error from the early comment: `ActiveRecord::StatementInvalid: TinyTds::Error: Incorrect syntax near the keyword 'COLLATE'.` Raising from ```database_statements.rb:361:in `do'```
I could execute `db:test:prepare` without errors by removing the option `collation` from `schema.rb` . from `t.string "foo", limit: 100, collation: "Latin1_General_CI_AI"` to `t.string "foo", limit: 100`
@wpolicarpo We're not connecting with two different database at the same time. But we did a migration from one legacy database, which collation is defined as `Latin1_General_CI_AI`. So, we end...
Hey guys. I think I'm facing the same problem with notifications about exceptions occuring outside "request/response" scope. I mean, for instance, CRON tasks and CQRS handlers could throws exceptions which...
Same problem here. Version: 4.1.0 SO: MacOS In my case, I need to use `/` char. Tried without escape and with escape (`\/`). And tried with and without quotes and...
It worked by using the following pattern: `--grep '"GET my/resource/foo"'` o/