Viacheslav Shevchenko

sure ``` ➜ mix ecto.migrate -r MyApp.RepoDynamo -n 0 Compiling 319 files (.ex) Generated app 20:17:37.673 [debug] ExAws: Request URL: "https://dynamodb.us-east-1.amazonaws.com/" HEADERS: [{"host", "dynamodb.us-east-1.amazonaws.com"}, {"x-amz-date", "20200707T171737Z"}, {"x-amz-content-sha256", ""}, {"x-amz-target", "DynamoDB_20120810.ListTables"},...

no problem - I am running this against the production environment - My config following ``` config :ecto_adapters_dynamodb, scan_tables: ["schema_migrations", "test_schema_migrations"] config :ignited, Ignited.RepoDynamo, migration_source: "test_schema_migrations", debug_requests: true ``` -...

Table `schema_migrations` being created in case `mix ecto.migrate -r MyApp.RepoDynamo -n 0` In case `mix ecto.migrate -r MyApp.RepoDynamo` only `schema_migrations` being created because raised the error. Also, I have tried...

Thank you for so fast feedback. I am going to create some workaround in my release task. I will think about PR if there will be time.

I got the same crashes. It happens when `gen_statem` in e.g `connected` state receives `{ws_send, frames()}` but the protocol is `gun_http` which doesn't have a `ws_send` function. Depending conditionally on...