Andreas Palm

Thanks for the report :smile: > I'm not sure if this is something you're actually able to fix on your side I did not know that you could provide a...

> With the release of 7.0.0, conform.nvim switched to a new configuration format Thanks for the heads up, we should definitely support this going forward then.

The recipe from mason-conform to [Run the first available formatter followed by more formatters](https://github.com/stevearc/conform.nvim/blob/master/doc/recipes.md#run-the-first-available-formatter-followed-by-more-formatters) posses a problem for this plugin. We need to get all possible formatters at run-time, in...

> its pretty bad TBH that this is not really supported. > > you should be able to configure conform.nvim as you see fit and mason-conform should not blow up...

> how did you go around not using it? I'm using https://github.com/WhoIsSethDaniel/mason-tool-installer.nvim to do the installation, and I keep my own conversion map for the tools that I use that...

Should be resolved by #6

We have been using these changes in production for our client for a couple of months now, no issues so far :ok_hand:

> As an aside, my proposed support for an `--init-sql` feature in [this thread](https://github.com/amacneil/dbmate/discussions/625#discussioncomment-12731209) could provide this same functionality by using `--init-sql "select pg_advisory_xact_lock(48372615)"`. > > Just another use case...

> > This PR addresses this by opening a separate database connection that starts a transaction just to hold the lock, so when the transaction is comitted or rollbacked, the...

> Session-level locks get released when the session ends, so even if the pod is killed, if the migration is still running and the session hasn't been killed with a...