go get dagger broken

[tawny valley]

Hello,
I tried to reimport latest change from main but i'm having this error

go get dagger.io/dagger@main
go: downloading dagger.io/dagger v0.2.35-0.20221021093240-fe3f9e22ec52
go: dagger.io/dagger@v0.0.0-00010101000000-000000000000: invalid version: unknown revision 000000000000

Any clue ?

[carmine nebula]

Hi @tawny valley,
I know that yesterday we were facing lots of issues regarding go module imports. Unfortunately, I wasn't there live. I don't know where we stand on the subject: @naive musk any clue ?

It is highly probable that the import path has changed temporarly

[spark ruin]

@raw trellis has been making some changes to go get dagger.io/dagger also. Not sure what the last update on that is

[tawny valley]

yeah i read some of the discussion but could found out how to fix it or if it is currently fixable on my side

[carmine nebula]

Could you please try: dagger.io/dagger/sdk/go/dagger (for today) ?
The aim is to go back to dagger.io/dagger afterwards

[limber kernel]

I think there's one more step needed to fully revert from the changes yesterday, I'll post in #maintainers

[tawny valley]

if it is temporary i can just wait it is no big deal

[tawny valley]

and also same error with "dagger.io/dagger/sdk/go/dagger"

[naive musk]

It won't be resolved soonish

it's linked to a go get issue that is acknowledged, but not taking care of by the Go team, yet (and it has been approved last year. so it is not a big priority for the Go team)

so for now we reverted back on just using 1 module, and access the SDK directly to its own subdirectory : dagger.io/dagger/sdk/go/dagger

let me confirm that

[limber kernel]

yeah I think the issue is the go mod names are incorrect though. Still trying to untangle it on my end

running go get -x dagger.io/dagger@fe3f9e2, I don't understand where it's getting v0.0.0-00010101000000-000000000000 from. The dagger.io/dagger/@v/list looks correct

[carmine nebula]

@zenith haven related

[zenith haven]

FYI I am seeing this

go: dagger.io/dagger@v0.2.36: parsing go.mod:
    module declares its path as: go.dagger.io/dagger
            but was required as: dagger.io/dagger

Isn’t there an issue with the first line of dagger’s go.mod ?

[limber kernel]

If you're wanting to use 0.2.36, go get go.dagger.io/dagger@v0.2.36 will work, but for the Go SDK that version will be too old

[zenith haven]

I only included dagger.io/dagger in my go source file. I don’t know where the version comes from, tbh 🤔

[limber kernel]

yeah the highest semver tag currently is 0.2.36. There was a 0.3.0-alpha.1 tag previously that got deleted

@zenith haven @tawny valley if you want to be unblocked and get on a recent-ish commit, go get github.com/dagger/dagger@535971db appears to work

[zenith haven]

Thanks a lot. I’ll try it 🙂

[limber kernel]

Actually the go.mod might still be funky there 😞

Stepping back a bit further, go get go.dagger.io/dagger@1d269ccc worked for me

[zenith haven]

thanks. It doesn't work for me. I can go get it, but a go build gives me this:

imports go.dagger.io/dagger: build constraints exclude all Go files in /Users/gaetan/go/pkg/mod/go.dagger.io/dagger@v0.2.35-0.20221020191106-1d269ccce644

[tawny valley]

Hello. I think this line might be the root cause of everything ? https://github.com/dagger/dagger/blob/a0117476aed916bf739f3330f3158645d2b93d90/go.mod#L6

[carmine nebula]

Hello,
We found a plan to fix everything ASAP. It shall be fixed today or tomorrow

[tawny valley]

Oh okay 😄

[tawny valley]

so i did a fork remove the line and do a go mod edit -replace=dagger.io/dagger@main=github.com/laupse/dagger@main and now it works 😄

[limber kernel]

If you're trying to build the cli, you'll want go build ./cmd/dagger 🙂

[raw trellis]

Everything should be working now

[zenith haven]

yeah ! Thank you 🙂 🙌
I'll try again today.

[zenith haven]

It Works!

🥳

good job! I consider this fixed. ✅

[neat onyx]

Yay! thanks @zenith haven

please let us know how it goes!