Are you still getting this error? Could | Dagger | Page 1

normal glade Jul 4, 2024, 11:06 AM

#

Platform: Windows 11

Clone the dagger repo:
cd dagger/dev
dagger develop
dagger call -m dev --source=.:default test all
I see this error:

PS H:\dagger\dev> dagger call -m dev --source=.:default test all
✘ initialize 6.4s
! input: module.withSource.initialize resolve: failed to initialize module: failed to call module "dagger-dev" to get functions: call constructor: process "go build -o /runtime ." did not complete successfully: exit code: 1

Stderr:
# github.com/dagger/dagger/dev/internal/build
internal/build/builder.go:309:17: not enough arguments in call to dag.Go
        have (*dagger.Directory)
        want (*dagger.Directory, string, string)
  ✘ Module.initialize: Module! 4.5s
  ! failed to initialize module: failed to call module "dagger-dev" to get functions: call constructor: process "go build -o /runtime ." did not complete successfully: exit code: 1
    ✘ exec go build -o /runtime . 4.4s
    ! process "go build -o /runtime ." did not complete successfully: exit code: 1
    ┃ # github.com/dagger/dagger/dev/internal/build
    ┃ internal/build/builder.go:309:17: not enough arguments in call to dag.Go
    ┃         have (*dagger.Directory)
    ┃         want (*dagger.Directory, string, string)

Error: input: module.withSource.initialize resolve: failed to initialize module: failed to call module "dagger-dev" to get functions: call constructor: process "go build -o /runtime ." did not complete successfully: exit code: 1

Stderr:
# github.com/dagger/dagger/dev/internal/build
internal/build/builder.go:309:17: not enough arguments in call to dag.Go
        have (*dagger.Directory)
        want (*dagger.Directory, string, string)

kind sparrow Jul 4, 2024, 7:28 PM

#

normal glade Platform: Windows 11 1. Clone the dagger repo: 2. `cd dagger/dev` 3. `dagger dev...

Try:

Clone the dagger repo
dagger call -m dev --source=.:default test all

normal glade Jul 5, 2024, 11:26 AM

#

still getting this error:

PS H:\dagger\dev> dagger call -m dev --source=.:default test all
✘ initialize 1.7s
! input: module.withSource.initialize resolve: failed to initialize module: failed to call module "dagger-dev" to get functions: call constructor: process "go build -o /runtime ." did not complete successfully: exit code: 1

Stderr:
# github.com/dagger/dagger/dev/internal/build
internal/build/builder.go:309:17: not enough arguments in call to dag.Go
        have (*dagger.Directory)
        want (*dagger.Directory, string, string)
  ✘ Module.initialize: Module! 0.4s
  ! failed to initialize module: failed to call module "dagger-dev" to get functions: call constructor: process "go build -o /runtime ." did not complete successfully: exit code: 1
    ✘ exec go build -o /runtime . 0.4s
    ! process "go build -o /runtime ." did not complete successfully: exit code: 1
    ┃ # github.com/dagger/dagger/dev/internal/build
    ┃ internal/build/builder.go:309:17: not enough arguments in call to dag.Go
    ┃         have (*dagger.Directory)
    ┃         want (*dagger.Directory, string, string)

Error: input: module.withSource.initialize resolve: failed to initialize module: failed to call module "dagger-dev" to get functions: call constructor: process "go build -o /runtime ." did not complete successfully: exit code: 1

Stderr:
# github.com/dagger/dagger/dev/internal/build
internal/build/builder.go:309:17: not enough arguments in call to dag.Go
        have (*dagger.Directory)
        want (*dagger.Directory, string, string)

kind sparrow Jul 6, 2024, 12:59 PM

#

you have to run it from the root of the git repo

normal glade Jul 9, 2024, 12:13 PM

#

normal glade still getting this error: ```powershell PS H:\dagger\dev> dagger call -m dev --s...

still this erro:

PS H:\dagger> dagger call -m dev --source=.:default test all
✘ initialize 2.9s
! input: module.withSource.initialize resolve: failed to initialize module: failed to call module "dagger-dev" to get functions: call constructor: process "go build -o /runtime ." did not complete successfully: exit code: 1

Stderr:
# github.com/dagger/dagger/dev/internal/build
internal/build/builder.go:309:17: not enough arguments in call to dag.Go
        have (*dagger.Directory)
        want (*dagger.Directory, string, string)
  ✘ Module.initialize: Module! 1.0s
  ! failed to initialize module: failed to call module "dagger-dev" to get functions: call constructor: process "go build -o /runtime ." did not complete successfully: exit code: 1
    ✘ exec go build -o /runtime . 0.9s
    ! process "go build -o /runtime ." did not complete successfully: exit code: 1
    ┃ # github.com/dagger/dagger/dev/internal/build
    ┃ internal/build/builder.go:309:17: not enough arguments in call to dag.Go
    ┃         have (*dagger.Directory)
    ┃         want (*dagger.Directory, string, string)

Error: input: module.withSource.initialize resolve: failed to initialize module: failed to call module "dagger-dev" to get functions: call constructor: process "go build -o /runtime ." did not complete successfully: exit code: 1

Stderr:
# github.com/dagger/dagger/dev/internal/build
internal/build/builder.go:309:17: not enough arguments in call to dag.Go
        have (*dagger.Directory)
        want (*dagger.Directory, string, string)

kind sparrow Jul 9, 2024, 12:17 PM

#

Does this ring a bell @ivory totem @robust trellis @soft rapids @neat umbra ?

robust trellis Jul 9, 2024, 12:20 PM

#

I'm not using test all because it's too flacky so nope, but when I run the command from the root of the repo, it executes the tests

kind sparrow Jul 9, 2024, 12:23 PM

#

@normal glade can you give us the outputs of:

git log -1

git status

ivory totem Jul 9, 2024, 12:31 PM

#

Yeah, I don't get that error. The error seems to suggest maybe a different version of the go module is being used on account of the difference in the signature of dag.Go. So that make me wonder which CLI version is being used, and which commit is cloned.

soft rapids Jul 9, 2024, 12:33 PM

#

kind sparrow Does this ring a bell <@768585883120173076> <@281874480651829250> <@796825768600...

No, I haven't seen this error before.

What OS are you using @normal glade ? PS H:\dagger makes me curious.

normal glade Jul 9, 2024, 12:44 PM

#

kind sparrow <@1081584998127255653> can you give us the outputs of: ```console git log -1 ``...

PS H:\dagger> git log -1
commit f9fd2993f5a96b3bb95f7559e810aafbd50cdd99 (HEAD -> main, origin/main, origin/HEAD)
Author: Jeremy Adams <jeremy@dagger.io>
Date:   Wed Jul 3 03:09:09 2024 -0700

    fix: correct exposed port from 8080 to 80 (#7815)
    
    Signed-off-by: Jeremy Adams <jeremy@dagger.io>
PS H:\dagger> git status
On branch main
Your branch is up to date with 'origin/main'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   dev/dagger.json
        modified:   dev/go.mod
        modified:   dev/go.sum
        modified:   go.mod
        modified:   install.ps1

no changes added to commit (use "git add" and/or "git commit -a")

normal glade Jul 9, 2024, 12:44 PM

#

soft rapids No, I haven't seen this error before. What OS are you using <@10815849981272556...

Windows 11

ivory totem Jul 9, 2024, 12:46 PM

#

You're behind a few commits. Can you undo the modifications in dev and go.mod and git pull to get latest commit?

kind sparrow Jul 9, 2024, 12:54 PM

#

If you want to run it independently of your local checkout, you can also reference the remote repo directly:

dagger call -m github.com/dagger/dagger/dev --source=https://github.com/dagger/dagger test all

#

Or, to run the remote dev module against a local source checkout:

dagger call -m github.com/dagger/dagger/dev --source=.:default test all

normal glade Jul 9, 2024, 4:53 PM

#

Its taking more time to execute

normal glade Jul 9, 2024, 4:53 PM

#

kind sparrow Or, to run the remote dev module against a local source checkout: ```console da...

tried this:

#

Is it normal?

soft rapids Jul 9, 2024, 4:59 PM

#

Yes. It is expected to take 40-50mins, but can take longer, all depending on the speed of your local disk. It is very disk intensive since it can boot up to 16 Dagger Engines inside Dagger in parallel. We normally run test custom and pick a subset of tests when running locally. Our CI runners which are IO optimised - c6id - take ~12mins to run this.

#Are you still getting this error? Could