Michael Vorburger
Michael Vorburger
I have been able to create an update for the `shasum` by doing the following (see #259 re. Legacy OpenSSL): ```bash $ NODE_OPTIONS=--openssl-legacy-provider yarn build $ yarn build:snap:postprocess ``` and...
https://pebbletemplates.io/wiki/guide/installation/ looks fine now.
I've debugged this a bit more, and it's `ghcr.io/devcontainers-community/features/bazel:1` which seems to be the one causing it (the `ghcr.io/devcontainers/features/java:1` appears irrelvant), I suspect that this should be easily reproducible with...
https://registry.bazel.build/modules/contrib_rules_jvm ? (I have NOT tried it.)
> Since F40 has rocm6 now > Fedora 40 include ROCm now in standard locations as far as I can tell. > It looks like the install script is looking...
> Worked fine in versions before 3.1.0 @vorburger , maybe due to mariadb update? Yeah, looks like the more recent MariaDB version has become "stricter" than the previous one... ERROR...
> @vorburger I am using the db persistently for the backend of a project so that would delete all the data if I understood it correctly, so no can't do...
Thread will wait for "mysqld: ready for connections." to appear in Console output of process Program
> I'm using mariadb4j-core version 2.6.0 @legnesi would you be able to upgrade to the latest version, currently 3.0.2?
Thread will wait for "mysqld: ready for connections." to appear in Console output of process Program
> @Eyzic The 3.0.2 is not in maven central. ==> #902 > I should normaly be in the JitPack repo (https://jitpack.io/#vorburger/MariaDB4j). But it look like it is not available ==>...
Thread will wait for "mysqld: ready for connections." to appear in Console output of process Program
> You need to look at (or post here) the full log, and see if there is any indication earlier than the failure that tells you why. I'm closing this...