The GitHub Actions job "CI" on grails-core.git/fix/qualified-session-connection-scope has failed. Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run: 076ff093245947f22b7f0dd15aeb014a63ecb5c7 / Scott Murphy Heiberg <[email protected]> Route the class's own GORM calls to the connection a qualified session or transaction opens Book.moreBooks.withTransaction { } opens the moreBooks session and transaction, but Book.list() and book.save() inside it resolved the default connection's API. On MongoDB the save was written to the default database, on Neo4j it went to the default server or failed with NoTransactionException, and on Hibernate 5 and 7 it failed with "No Session found for current thread". withSession, withNewSession, withStatelessSession, withTransaction and withNewTransaction on a named connection's API now run their closure in GormRegistry.withConnectionScope for that connection, as withConnection does. The default connection's API undoes an enclosing scope for its block, so Book.'default'.withSession { } nested in one reaches the default connection. A qualifier that names no connection, such as a DISCRIMINATOR tenant id from withTenant, is left alone. The refresh-lock specs relied on the old routing to reach the default connection from inside a secondary block, and now name it. Report URL: https://github.com/apache/grails-core/actions/runs/35691414351 With regards, GitHub Actions via GitBox
