I recently upgraded the Meltano version we are using to the latest CLI, and I've started to see a flaky error appear in my integration tests. On each test run we create a new postgresql db container for Meltano, run the Meltano
upgrade
command to update the schema, and then run our tests. I am finding occasionally that the following error is thrown from Meltano when running the
meltano el
command due to migrations being applied automatically and then failing. I am a bit confused as the migrations should already be applied to the db at this stage, and I haven't seen this behaviour before where Meltano is attempting to run the migrations anyway, anyone else seen this issue?