Ghlen Nagels

Thank you for the offer! - There is, actually. It would be a great help if you can simplify the test that breaks, so it is reproducible with the client...

Yes :+1:, I'll be working on some other projects today, but will circle back to this tomorrow and tonight

Yes, it's supposed to be a comma seperated list of uri's to connect to. (eg: bolt://localhost,http://neo4j:test@neo4j:7475)

Does it work if you use client instead of testkit backend?

Testkit backend does not use the .env explicitly meaning you have to load it manually during bootstrapping (eg bootstrap_override_with_dotenv.php used by some workers of github actions)

Very strange, I can run the tests without any problems. I just double-checked. This is a great error though, are you using a different setup with Neo4j or did you...

Does it keep giving not a leader errors on subsequent reruns?

I can't see every error, but the first one is a bug in the neo4j routing algorithm which I haven't seen in ages

Got it. The NEO4J_CONNECTIONS are misconfigured Bolt does not autoroute queries, so it tries to reach core1, which may or may not be a leader at that moment. You need...

Can you try it with this one? `NEO4J_CONNECTIONS=bolt://neo4j:test@neo4j,neo4j://neo4j:test@core1,http://neo4j:test@neo4j`