#Not that it helps you at this moment,

1 messages · Page 1 of 1 (latest)

desert rain
#

Hey @rocky shard going back to this - its still not wokring for me but I am seeing something very very strange. This module lives in a main repo called levlaz/daggerverse

When I try to run dagger mod install --progress=plain github.com/levlaz/daggerverse/opentofu

I see this in my output

levlaz@Levs-MacBook-Pro ci % dagger mod install --progress=plain github.com/levlaz/daggerverse/opentofu
1: connect
1: > in init
1: starting engine
1: starting engine [0.20s]
Connected to engine 8804399291f5 (version v0.9.7)
1: starting session
1: [1.45s] OK!
1: starting session [0.34s]
Dagger Cloud URL: https://dagger.cloud/runs/bfe594b1-8412-49fa-b9a8-a1246c9f981c
1: connect DONE

6: git://github.com/sagikazarmark/daggerverse#20e8626c9f25d570e6321765d496643736d76ee5
6: > in commit
6: git://github.com/sagikazarmark/daggerverse#20e8626c9f25d570e6321765d496643736d76ee5 DONE

6: git://github.com/sagikazarmark/daggerverse#20e8626c9f25d570e6321765d496643736d76ee5 CACHED

It looks like its pulling from Marks daggerverse repo for some reason :/

rocky shard
desert rain
#

derp - sorry for the false alarm this has nothing to do with the problem ...

#

I am indeed depending on Mark's golangci-lint package - sorry got confused

rocky shard
#

No worries! 🙂

desert rain
#

@fiery needle unfortunately my LD module also has this issue 😦

If you get a chance could you take a peak and see if there is maybe something I did wrong on my end? It’s strange because I have a bunch of modules in that repo and some of them work just fine.

fiery needle
#

I cloned your daggerverse repo down, made a new directory foo inside and init'd a new go mod.

Then from there I ran
dagger mod install of your opentofu and got:

54: generating go module: OpenTofu ERROR: load package ".": package name is empty

49: exec /usr/local/bin/codegen --module . --propagate-logs=true --introspection-json-path /schema.json
49: > in withSource > asModule > withSource > directory
49: [0.93s] Error: load package ".": package name is empty
49: exec /usr/local/bin/codegen --module . --propagate-logs=true --introspection-json-path /schema.json ERROR: process "/usr/local/bin/codegen --module . --propagate-logs=true --introspection-json-path /schema.json" did not complete successfully: exit code: 1
Error: failed to automate vcs: failed to get vcs ignored paths: input: resolve: module: withSource: load "github.com/levlaz/daggerverse/opentofu@a49946563219c1986c204e6cf657c063e8a94756": failed to get modified source directory for go module sdk codegen: process "/usr/local/bin/codegen --module . --propagate-logs=true --introspection-json-path /schema.json" did not complete successfully: exit code: 1
input: resolve: module: withSource: load "github.com/levlaz/daggerverse/opentofu@a49946563219c1986c204e6cf657c063e8a94756": failed to get modified source directory for go module sdk codegen: process "/usr/local/bin/codegen --module . --propagate-logs=true --introspection-json-path /schema.json" did not complete successfully: exit code: 1

Stdout:

Stderr:
Error: load package ".": package name is empty
#

I get the same thing with my foo mod dir outside of your daggerverse

#

@desert rain it keeps complaing about your dagger.json not being there...

I wonder if there is an issue with you using mixed case in your mod name...

{
  "name": "OpenTofu",
  "sdk": "go"
}
#

not an issue with

{
  "name": "launchdarkly",
  "sdk": "go"
}
#

getting similar/same errors regardless with that 👆 on dagger mod install

desert rain
#

This has something to do with a monorepo structure because when I port the same exact code to a standalone repo everything works fine :/

desert rain
#

If I prune my entire local docker volume cache things seem to work.

#

I paired with @median canyon for a bit and he thinks this issue may be related to #maintainers message

fiery needle
#

for the record, no issue with python mods that we tried, just golang