sterankin
sterankin
Thanks @hassy, note that the Datadog integration works fine _without_ a DD_APP_KEY when _not_ using Docker. Its only when you run in the Docker container that the error occurs. I...
Thanks for the comment - I tried adding this but I still got the error when I chose a primary key in the model. I guess the driver code is...
Thanks for the reply, that looks like a potential solution, however when I manually run the SQL: SELECT 1 FROM SYSIBM.SQLPRIMARYKEYS WHERE TABLE_NAME = 'my_table_name'; It returns 0 rows. Does...
It happens randomly in our sidekiq job, when we connect to db2, it doesn't happen on any particular query but it is generally the first query where we try to...
The solution I have found through trial and error is to add the following to the jdbc:as400 database connection string: socket timeout=20000;login timeout=20000;thread used=false; I still get the SQLException, but...
Just to add an update, I am now trying to use the bundler config option, which allows you to tell bundler where to install the freetds libraries from. So my...
Ok the path was wrong, I was able to use the correct path to the compiled freetds folder: BUNDLE_BUILD__TINY_TDS: "--with-freetds-dir=/tmp/app/vendor/freetds" But its now failing with: ``` OUT] Starting health monitoring...
I am also receiving this error on Cloud Foundry (which is similar to Heroku) on 0.54.2. ``` gem 'ddtrace', require: 'ddtrace/auto_instrument' gem 'dogstatsd-ruby' ``` ``` DD_TRACE_ENABLED: true DD_RUNTIME_METRICS_ENABLED: true ```...
> @sterankin you mention "during deployment"; I wonder if your situation is similar to the Heroku issue where during push/buildpack build a few errors can show up in the log...
@brandon707 did you ever manage to resolve this?