James Ward

I'm using 4.6.2 and postgres and cannot replicate this. Commenting and subscribing for when the minimal repo is up!

I've run into this as well. The biggest issue I can see here is that two query runners can effectively run at the same time - starting transactions, closing transactions,...

Thinking about it.. the lock is effectively just a pool with a size of 1 anyway :)

Ok - lock breaks a great number of tests because MANY assumptions in our codebase are there on operating on multiple query runners. I've implemented a transaction queue per suggestions...

I started work on this as a feature over here -> https://github.com/imnotjames/portr/tree/feat/proxy-auth But I decided it'd be a good idea to open up the issue to get feedback before I...

I could implement a trusted IP mechanism but after digging into this further it really increases the scope of the work by a lot. Perhaps we first enable the header...

I do have something working over in my branch. I've built it in a new docker file and have deployed it as my local instance of portr. Works great behind...

Sure thing. I think in an ideal world portr would integrate with OIDC providers and handle authentication that way. With that, you could hook up to everything from Keycloak to...

#247 is a much smaller simpler change that also resolves this problem

The one-liner in #247 also resolves this