5 0 2 is out with a bunch of fixes

Question

5 0 2 is out with a bunch of fixes <https kotest io docs changelog html>

thanksforallthefish · Answer

I just merged a dependency update to 5 0 1 5 minutes ago disappointed

sam · Answer

ha sorry

sam · Answer

Now you get to make another commit

Big Chungus · Answer

Are the new MPP engine setup docs available already

sam · Answer

No need to do that still help is always welcomed

sam · Answer

Example project here <https github com kotest kotest examples multiplatform>

Big Chungus · Answer

I would if I wouldn t need the docs myself to understand the changes D

sam · Answer

hah

sam · Answer

definitely by the end of the weekend I have time on sunday if not before

Big Chungus · Answer

Can you make a release like announcement on < CT0G9SD7Z|kotest> once they re out so I could stop bugging you with the same questions

sam · Answer

yep

Big Chungus · Answer

Much appreciated

sam · Answer

reminders set

Peter · Answer

still having my testcontainers startup issue with 5 0 2 cry

sam · Answer

yeah I m publishing 1 1 0 which will work with 5 0 2

sam · Answer

1 1 0 is out if you want to try it

Peter · Answer

ok cool eyes

Peter · Answer

still the same problem unfortunately disappointed

sam · Answer

can you recap your issue

Peter · Answer

yep working on a minimal case brb

Peter · Answer

```class UserSpec WordSpec private val network = Network newNetwork private val postgresContainer = PostgreSQLContainer DockerImageName parse postgres 13 withDatabaseName config databaseConfig databaseName withUsername config databaseConfig username withPassword config databaseConfig password value withExposedPorts 5432 withNetwork network init listener postgresContainer perSpec Users Route should override fun beforeSpec spec Spec println $ postgresContainer firstMappedPort ```

Peter · Answer

the `postgresContainer firstMappedPort` fails with

Peter · Answer

``` Caused by java lang IllegalStateException Mapped port can only be obtained after the container is started at org testcontainers shaded com google common base Preconditions checkState Preconditions java 174 at org testcontainers containers ContainerState getMappedPort ContainerState java 142 at java base java util Optional map Optional java 265 ```

sam · Answer

the perSpec listener is probably firing after your before spec

Peter · Answer

100 worked in 4 6 3 100 failure in 5 x

sam · Answer

the order is not guaranteed and probably changed between releases

Peter · Answer

cry

sam · Answer

we can fix that by moving to a test case extension

Peter · Answer

i use the `beforeSpec` to setup the connection pool amp do flyway etc

sam · Answer

Yeah that s fine you just need the container to be guaranteed to fire first I ll fix it might take 30 mins

Peter · Answer

thank you

sam · Answer

If you use the new jdbc container stuff then you should be good ```class UserSpec WordSpec private val network = Network newNetwork private val postgresContainer = PostgreSQLContainer DockerImageName parse postgres 13 withDatabaseName config databaseConfig databaseName withUsername config databaseConfig username withPassword config databaseConfig password value withExposedPorts 5432 withNetwork network val ds = install JdbcTestContainerExtension postgresContainer maximumPoolSize = 8 minimumIdle = 4 init Users Route should override fun beforeSpec spec Spec println $ postgresContainer firstMappedPort ```