Golang News

Goland tip of the day: when Make run configurations dont find "go" #goland

Sun, 14 Oct 2018 10:27:00 +0000

In a Goland 2018.3 EAP run configuration, a Makefile run configuration finds the go binary on macOS, but not on Ubuntu, causing lines tasks this one builds 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

Let's fix it...

4 points posted by FGM

GoLand tip of the day: clean up leftover cache and log folders #goland

Sat, 08 Dec 2018 17:26:00 +0000

When GoLand is upgraded from one version to the next, the deployment process adds a new set of configuration, cache, and log directories. But it does not remove the versions associated to the previous versions of the IDE, to ease rolling back to the previous version if an upgrade happens to cause an issue.

So after some time, removing these now-unused folders will regain some disk space, possibly more than 1 GB. Here are their respective locations and content on macOS...

2 points posted by FGM

How to debug a second test run ? #test #testing #delve #goland #debugging

Thu, 09 Jun 2022 11:22:00 +0000

Sometimes, tests can succeed on the first run and fail on subsequent ones, or with the -shuffle flag. But then, how can one debug them using the builtin Delve in GoLand while run configurations only run tests once ? 1 points posted by FGM

Comment déboguer la seconde exécution d'un test #delve #goland #debugging

Wed, 01 Jun 2022 17:36:00 +0000

Parfois, des tests peuvent réussir à la première passe et échouer à la suivante, ou dans un autre ordre. Mais comment les déboguer avec Delve et GoLand alors que les configurations d'exécution n'exécutent les tests qu'une seule fois ? 1 points posted by FGM