Oliver Santana

Hello @hicnar , We are trying to reproduce this without success. Does this happen when the bean is injected directly in the method as well or just in the constructor?...

We tried with that distribution too and it works fine. Could you provide a small sample project to allow us to reproduce it?

Hello @jmayday, thanks for raise the issue. You are right, we have a two step validation process to avoid taking the lock when it isn't necessary, and when there is...

Hello @gaganis , we have been waiting to fix it in the next release because we have refactored the executor, so we expect to release it in the next days....

Hello @gaganis , we have released Mongock's version 5.2.1, and it fixes the log inconsistency. Please could you try it and let us know? Thanks.

Hello @oliverlockwood , thanks for raising the issue. We'll take a look and let you know as soon as possible.

Hello @oliverlockwood , When a ChangeUnit execution fails it will write something like this in the output log: ``` 2024-03-26 11:32:32.998 INFO 60861 --- [ main] i.m.r.c.executor.ChangeLogRuntimeImpl : method[io.mongock.examples.mongodb.springboot.quickstart.migration.ClientUpdaterChangeUnit] with...

@oliverlockwood released in Mongock's version 5.4.2.

Hello @fnordian , First mention that this wasn't failing in previous versions of Mongock(v4) because although we were storing the data(`timestamp` and `executionMillis`), we weren't reading it. Now, in version...

Hello @Vladcorjuc , we couldn't reproduce this error. It should be caused by something specific to your configuration, environment o even MongoDb Atlas. Could you share any additional detail about...