How to edit Ansible templates in GoLand, PhpStorm, or other JetBrains IDEs: think outside of the box ! There is a free solution...
The problemIn a GoLand 2018.3 EAP run configuration, a Makefile run configuration finds the
gobinary on macOS, but not on Ubuntu, causing make targets like this one to fail:
# 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 ?
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.
So join me there :-)
While exporting a project from Unfuddle in order to import its issues to Jira, I took a look at the other files beyond
backup.xml and the
media/ directory. Turns out that when Unfuddle provides you with a project backup, it includes the repositories in an undocumented (on their site, at least) format, under the
dmp file extension. Let's find out how to actually use these.
When auditing or reviewing an unknown code base, I often have to decide which files to examine in priority. Beyond the usual heuristics for Drupal projects (hint: look at templates in D7), how can one find the parts most likely to contain problems ? This simple command set can help pinpoint troublemaking files quickly.
While porting (well, actually rewriting) an old PHP library to Go, I had to use a CRC (cyclic redundancy check) on a buffer. In old-school PHP, the standard is well established since PHP 4: just use
crc32 from the
strings package, and beware of the sign bit or, to be a bit more current while still compatible, use the
hash() function from the
hash package, like this example:
If you program in Go, you've probably written a lot of packages, and probably split packages in subpackages. Maybe even more than idiomatic Go would really advise... And you may have been grumbling just like I did at the fact that the
go test command requires a list of packages, and does not recursively dive into all the subpackages, like PHPunit would, and does not seem to have a working recursion flag.
I've long been receiving quite high volumes of comment spam on this blog, which is why comments have always been pre-moderated. And, of course, there is usually not much to think of it. Not so with one of the spam messages posted today, which unwittingly provided an unexpected insight into the current mechanisms uses by spammers.