#declaration not found

1 messages · Page 1 of 1 (latest)

leaden pewter
#

Just tried locally (on main branch), seems to work as expected. Never encountered it though, sorry 😢

umbral pumice
#

so weird. I'm gonna try from a new clone to try and remove the containers

steel osprey
#

Did you fix it ever @umbral pumice

umbral pumice
#

So, I was working on my desktop computer again, no problem. But on my laptop, it still doesn't work.
I removed the dagger buildkit containers + removed the cache from ~/.cache/dagger. Didn't change anything.
The only thing that was different between those 2 computers was the multiplatform setup, so I ran the binfmt util from tonii, but didn't make a change.

It seems it's only related to mage.

#

I'm gonna check my version used on the laptop vs the one on the desktop. Maybe the module cache have different version and MVS didn't need to update the desktop?

#

Anyway, out of that, I saw the internal/mage dir, and it's a little bit messy with all the build flags and different packages in the same directory. Can we make it better/clearer @craggy tendon ? It's a little bit confusing

#

I'm gonna try to compare the module cache version I have to see if it's that. Other than that, I'm out of options except digging into mage codebase

umbral pumice
#

Finished checking. Exact same version, using mage v0.14.0, but completely different behaviour

#

weirder even

~/go/pkg/mod/github.com/magefile/mage@v1.14.0$ go run bootstrap.go 
Error parsing magefiles: failed to parse directory: magefile.go:29:1: expected declaration, found func (and 1 more errors)
exit status 1
#

That's the official documentation of mage.
I removed the mage I already had on the computer

leaden pewter
#

Do you want to pair/a rubber duck in 30 min?

umbral pumice
#

I'm gonna switch task now. I'll get back to it tomorrow.

umbral pumice
#

We investigated right now.
On a new VM, with the latest Go and docker correctly installed, it works.
But on my laptop, I still have this weird error. Seems related to mage only, but cleaning the pkg/mod cache doesn't seem to solve anything. And I have the same go env on both laptop and desktop, as well as the same env (except the X graphical env var).

I thought it was the mix of multi package + multi build tag in the same dir that caused that, so I splitted in different directories, but to no avail.