feat(go): add basic driver logging

[lidavidm]

Fixes #492.

[lidavidm]

Bah, the experimental slog requires Go 1.20?

[lidavidm]

@zeroshade how do you feel about bumping us to Go 1.20 or 1.21? I think the main problem will be Linux packaging jobs where we won't be able to use the system golang...

[lidavidm]

Either that, or we can do build tag shenanigans to only enable this on Go 1.20?

[lidavidm]

It looks like Arrow itself was bumped to Go 1.20: https://github.com/apache/arrow/blob/main/go/go.mod

[zeroshade]

Arrow currently maintains compatibility with go1.17-go1.20. But as of apache/arrow#37637 we're dropping explicit compatibility with go1.17-go1.18. We're still keeping compatibility with go1.19 though, using build tags.

What we could do here is put together a small interface and then use build tags to use https://pkg.go.dev/golang.org/x/exp/slog for go1.19 and slog directly for go1.20+ similar to how we handle json in Arrow for tinygo vs non-tinygo

[lidavidm]

It looks like slog works on 1.19 too so I'll see about bumping to 1.19 here

[lidavidm]

Once I get this working I'll split out the version bump into a separate PR so that it's clear

[paleolimbot]

Is there a canonical place in the repository where this value could be scraped? I am pretty sure I can make this automatic so that you don't have to do the version bump every time.

[lidavidm]

We could use the .env but it's not in sync with everything else anyways (I guess it only affects docker-compose)

[lidavidm]

hmm, ubuntu-jammy fails because we install golang-1.20 but the package depends on golang. Let's see if we can finagle that...

[lidavidm]

Windows verification is failing since libprotobuf now has a runtime dependency on gtest, and so when our verification script tries to remove it (since we want to use bundled gtest on windows) it also clobbers half our conda environment

conda-forge/libprotobuf-feedstock#186

[lidavidm]

@kou do you know how to install golang-1.20 on Ubuntu Jammy and then have the APT package build be OK with having that installed in place of golang?

I also tried installing both golang and golang-1.20, but then go 1.18 ends up first on PATH and I couldn't get update-alternatives to work with go.

[lidavidm]

Hmm, let's see if alternative dependencies are the right thing to do...

[lidavidm]

Alright, now the problem is that the golang-1.20 package doesn't add itself to PATH.

[zeroshade]

@lidavidm you should be able to use this PPA to install golang-1.20

sudo add-apt-repository ppa:longsleep/golang-backports
sudo apt update
sudo apt install golang-go

[lidavidm]

I don't think we want to ship binaries that depend on a PPA (and Go 1.20 is in the repos, just have to finagle the configuration)

[zeroshade]

I didn't know there was an official package for go1.20 in the jammy repos

[lidavidm]

https://packages.ubuntu.com/jammy-updates/golang-1.20-go

[lidavidm]

OK, so long as the apt changes look OK, I'll split the Go version bump into a new PR, then come back here once that's merged

[kou]

+1 for APT related changes.

[lidavidm]

Thanks Kou! Split into #1053