@Mark Takata (Adobe) OK got two repos for those issues I spotted. Baseline: https://github.com/adamcameron/cf2021_and_mariadb CF2021 - all tests green, no issues Test: https://github.com/adamcameron/cf2023_and_mariadb CF2023 - both the graphql issue and the DSN one. This is almost identical to the 2021 one, except where it needs to say "2023". Install / usage instructions in readme.md for both.

Emailed this to the team and haven't heard back yet. @Bagish Mishra can you also flag this one for discussion?

Cheers for the follow-up, @Mark Takata (Adobe). @Bagish Mishra as well as following-up internally, can you pls feed-back results here too? The Docker image ain't usable straight out of the box ATM, which I think is is probably something quite important to CF2023?

ACK @Mark Takata (Adobe) @Adam Cameron

@Bagish Mishra any movement on this? Also cc @Mark Takata (Adobe) and @guustnieuwenhuis

we are looking into the issue, most likely this will be part of the next update coming in Sep 23

Given this is only a problem in a dockerised environment, is this not "just" a problem with the Docker image, rather than with CF itself? So not really something for a CF updater?

i meant the fix for it to be available in coming CF-update planned in Sep month

It's almost as if you didn't read what I just asked. Instead you just decided to repeat yourself. 😕

Adam, the issue is not something that could be fixed by pushing a new docker image. There is potentially a core issue having to do with several packages not playing nicely with each other.

Ah look at that! A coherent explanation (thanks!) instead of a brush off. Cheers Mark. Might be a comms lesson to take back to the team there.

I'd have to check exactly how they repro'd it. Normal off the shelf installs seem to work fine, they tried explaining it to me last night, but I've had 2 hours of sleep the last 3 days and that was after a day that started at 5am and ended at 11pm, so I think I missed some of the subtleties. I need to see if there's some way to work around the issue in containers but thus far that's the only place it is showing up when running CF in anger, so to speak.

Gotcha. Again: excellent technical engagement.