@Mark I've been unable to upgrade to | Dagger | Page 1

tranquil flare May 2, 2025, 3:44 PM

#

Stderr:
/src/shared/dagger/awscli/sdk/src/module/introspector/dagger_module/module.ts:278
      throw new IntrospectionError(
            ^


IntrospectionError: could not resolve type reference for AwsCli.
    at DaggerModule.resolveReferences (/src/shared/dagger/awscli/sdk/src/module/introspector/dagger_module/module.ts:278:13)
    at new DaggerModule (/src/shared/dagger/awscli/sdk/src/module/introspector/dagger_module/module.ts:134:10)
    at scan (/src/shared/dagger/awscli/sdk/src/module/introspector/index.ts:18:18)
    at async connection.LogOutput (/src/shared/dagger/awscli/sdk/src/module/entrypoint/entrypoint.ts:17:26)
    at async <anonymous> (/src/shared/dagger/awscli/sdk/src/connect.ts:44:11)
    at async withGQLClient (/src/shared/dagger/awscli/sdk/src/common/graphql/connect.ts:24:12)
    at async <anonymous> (/src/shared/dagger/awscli/sdk/src/connect.ts:40:9)
    at async connection (/src/shared/dagger/awscli/sdk/src/connect.ts:38:5)
    at async entrypoint (/src/shared/dagger/awscli/sdk/src/module/entrypoint/entrypoint.ts:11:3) {
  cause: undefined,
  code: 'D110'
}

Node.js v22.11.0

frigid haven May 2, 2025, 3:46 PM

#

@night hemlock could it be a bundling issue?

harsh root May 2, 2025, 3:51 PM

#

The stack looks maybe related to this 0.18.5 typescript codegen issue I've been facing too https://github.com/dagger/dagger/issues/10300

GitHub

🐞 Missing dependencies in Typescript codegen · Issue #10300 · ...

What is the issue? My typescript module does not have it's dependencies generated in it's client Dagger version 0.18.5 Steps to reproduce When I run my typescript module, it fails on dag.&l...

rocky aurora May 2, 2025, 4:58 PM

#

Would it help if I updated the dagger version in my daggerverse repo?

harsh root May 2, 2025, 5:04 PM

#

If it is the same bug as mine then no it wont help, I don't have any workaround other than using 0.18.4

night hemlock May 2, 2025, 7:50 PM

#

I'll have a look on Monday (currently in PTO), that's strange our CI didn't catch that problem, will be my 1st priority

night hemlock May 5, 2025, 11:04 AM

#

@rocky aurora @harsh root @fair bridge @frigid haven

Not directly bundle issue, I forget to handle path difference between bundle/vendored version and integrations tests were using the default setup so it was using the correct bundle.

I already fixed that issue in a PR that came right after the bundle one but it got merged after 0.18.5 release.

I left more details on the issue: https://github.com/dagger/dagger/issues/10300#issuecomment-2850635727

There are 2 ways to solve it:

Keep 0.18.4 until 0.18.6 is released
OR
Switch to bundle mode https://docs.dagger.io/configuration/modules/#bundled-or-vendored-sdk

tranquil flare May 6, 2025, 10:08 AM

#

@night hemlock if bundle is the default then i believe i'm already using bundle mode -- or are you saying my dependency should switch to bundled mode

#@Mark I've been unable to upgrade to