The GitHub Actions job "CI - Groovy Joint Validation Build" on 
grails-core.git/fix/embedded-mongo-backend-reuse-8.0.x has succeeded.
Run started by GitHub user codeconsole (triggered by codeconsole).

Head commit for run:
1e74b1afc1c80d168a75b3d11676d1c588935974 / Scott Murphy Heiberg 
<[email protected]>
Reuse a server only when it is running the backend being asked for

A restart is handed the server this JVM already started when the settings it
asks for match the ones it was started with. The backend was not among them, so
switching from the in-memory reimplementation to flapdoodle -- or back -- while
changing nothing else quietly kept the old server. The application asked for a
real mongod and carried on against the in-memory one, which does not implement
transactions, change streams or $text, so the failure arrives later and
somewhere else.

The check already compares the version, which the in-memory backend ignores
entirely, so the omission was of the one setting that decides what the server
actually is.

The backend is resolved before the reuse question rather than inside start(),
since it is part of that question, and the name it was started with is kept
alongside the settings.

A restart that asks for a backend whose library is absent now says so even when
a server is already running, instead of being handed that server. That is the
same answer it would have given had nothing been running.

Report URL: https://github.com/apache/grails-core/actions/runs/32791118989

With regards,
GitHub Actions via GitBox

Reply via email to