Computing

Let's face it, with the velocity of major version upgrades in Drupal having increased a lot since Drupal 9, many projects - both themes and modules - do not yet have releases for Drupal 11, or even Drupal 10 for some of them, although they may have automatic compatibility patches / issue forks ready to be committed for months. Alas, just because they do not declare Drupal 11 (or 10) compatibility in their composer.json (or they don't have one yet, looking at you Bartik), composer require with a patches clause won't work because Composer checks for compatibility without the patches. So how can we use all that perfectly ready code that doesn't have a correctly labeled release ?

If you are using the Gogs git server and just apply updates automatically without Reading The Fine Manual, your server became vulnerable with the 0.13 releases, enabling vulnerabilities described by CVE-2024-39930, CVE-2024-39931, CVE-2024-39932, CVE-2024-39933. See how to fix it.

An easily missed feature in Jenkins is the bundled linter for Jenkinsfiles.

While there are many examples about how to use it with cURL, I could not find any using HTTPie, which I find much more convenient in general than cURL. So, after some fumbling due to the little documented expectations of the validator, here is the solution showing how to validate a Jenkinsfile from the CLI:

After almost one year with an Apple Silicon macBook, I eventually got my first actual problem caused by the architecture : trying to deploy the Flagr Open Source feature flags service, the docker deployment failed like with an image error. The fix turned out to be fairly simple:

While working on i18n in Go with the x/text package, I had to dive into the subtleties of language tags (RFC5646) and their filtering/lookup (RFC4647) and, would you believe it ? things are much less simple than we usually take them to be, even in a real-life i18n environment like Drupal 8/9/10.

How to edit Ansible templates in GoLand, PhpStorm, or other JetBrains IDEs: think outside of the box ! There is a free solution...

The problem

In a GoLand 2018.3 EAP run configuration, a Makefile run configuration finds the go binary on macOS, but not on Ubuntu, causing make targets like this one to fail:

client/test.wasm: client/main.go
	# Building WASM
	GOARCH=wasm GOOS=js go build -o client/test.wasm client/main.go

/usr/bin/make -f (some edited path)/Makefile client/test.wasm
/bin/sh: 1: go: not found
make: *** [client/test.wasm] Error 127

Simple enough to fix...

As you may have noticed if you are a regular here, I just refreshed the theme on this site to a custom theme built on Bartik. And since Chrome had just been updated, I took the newly updated performance audit.

What more to say ?

The problem

When using MySQL from the CLI, the -e flag comes in handy to execute MySQL commands directly in bash, like mysql -uroot -p -e "SHOW DATABASES;". Which gives nicely formatted output like:

So DrupalCon Europe is out for 2018. But that does not mean a EU-level event does not exist, to bind the community beyond the specialization of DevDays, FrontEnd United, CxO, GovDays, and all the DrupalCamps. Drupal Europe is that event, and to support the community who wants to prove a large Drupal conference can reasonably happen after all the trouble the Drupal Association had with it, the best way it to register for the conference.

ASAP.

So join me there :-)