#Client not found with v0.18.3

1 messages · Page 1 of 1 (latest)

silver flax
#

After upgrading from v0.18.2 to v0.18.3 I'm getting this error when accessing a private module in my Gitlab CI pipeline:

...
10  : │ load module
11  : │ │ finding module configuration DONE [0.9s]
20  : │ │ initializing module
21  : PythonSdk.moduleRuntime(
21  : │ │ introspectionJson: no(digest: "sha256:ce0cd4c2741a4fd47399cb3bf734e84a147ecdddb59e8753343926c7c4332ed8"): Missing
21  : │ │ modSource: no(digest: "xxh3:eb9be81d910e4bbd"): Missing
21  : │ ): Container!
21  : PythonSdk.moduleRuntime ERROR [0.1s]
21  : ! failed to create secret transfer post call: failed to get source client secret store: client "vayybt5lvbnv4t2yk5tw31w7g" not found
22  : ModuleSource.asModule: Module!
22  : ModuleSource.asModule ERROR [0.1s]
22  : ! failed to load dependencies as modules: failed to load module dependencies: select: failed to get module runtime: failed to call sdk module moduleRuntime: select: failed to create secret transfer post call: failed to get source client secret store: client "vayybt5lvbnv4t2yk5tw31w7g" not found
...

Does anyone know what this error means and have any hints on how to debug it?

dark thorn
#

It's likely a bug related to some internal changes in v0.18.3.

@silver flax are there any more details you could share? I know it involves a private module so you can't share the full code, but does this happen every time? Or is it inconsistent?

dark thorn
#

Ah actually, I just tried a few things in our integ test suite and think I managed to repro this. Seems like it involves calling a module that has a dep on a python module sourced from a private git repo, which is a particular permutation our tests were missing.

Will figure out and fix, ideally for the v0.18.4 release going out tomorrow. Thanks for the report!

silver flax
#

Thanks for having a look. Glad you could reproduce the issue. Would have setup a MRE instead. Yes, I can confirm that the issue is reproducible all the time with different private Python modules dependencies.

dark thorn
dark thorn
silver flax
#

Many thanks for the quick resolution. I just integrated v0.18.4 into our pipelines and can confirm that everything works again. No apologies needed—you all are doing an excellent job providing wonderful open-source software!

zinc narwhal
#

not sure if related but now my pipelines are failing with

✔ connect 0.3s
✘ load module 1.7s
! failed to serve module: input: moduleSource.asModule failed to call module "btd" to get functions: call constructor: process "uv pip install -e ./sdk -e ." did not complete successfully: exit code: 2
│ ✔ finding module configuration 0.5s
│ ✘ initializing module 1.2s
│ ! input: moduleSource.asModule failed to call module "btd" to get functions: call constructor: process "uv pip install -e ./sdk -e ." did not complete successfully: exit code: 2
│ │ ✘ ModuleSource.asModule: Module! 1.2s
│ │ ! failed to call module "btd" to get functions: call constructor: process "uv pip install -e ./sdk -e ." did not complete successfully: exit code: 2
│ │ │ ✔ module SDK: load runtime 1.1s

Error logs:

✘ Container.withExec(args: ["uv", "pip", "install", "-e", "./sdk", "-e", "."]): Container! 0.5s
Using Python 3.12.10 environment at: /usr/local                                                                                                                                                                                     
error: Distribution not found at: file:///src/xxh3:2a8a71606afc0f8a/.github/ci/btd/sdk                                                                                                                                              
! process "uv pip install -e ./sdk -e ." did not complete successfully: exit code: 2
#

using 0.18.4 btw

lyric tangle
coarse tiger
#

It's a regression for older modules still using requirements.lock.

lyric tangle
#

Out of curiosity what has replaced the requirements.lock?

zinc narwhal
#

is this something on dagger side or our module side? afaik we dont have or push requirements.lock 🤔

coarse tiger
coarse tiger
zinc narwhal
# coarse tiger If you get that error you are. Maybe it's from a dependency. There's a workaroun...

can you point me to the workaround please? we dont have any requirement.lock neither the sdk been commited this are our dagger.json

{
  "name": "btd",
  "sdk": "python",
  "engineVersion": "v0.17.2"
}

and pyproject.toml

[project]
name = "btd"
description = "Build, Test and Deploy"
version = "1.0.1"
requires-python = ">=3.12"
dependencies = [
    "dagger-io",
    "requests>=2.32.3",
    "botocore>=1.35.62",
    "boto3>=1.35.62",
]
coarse tiger
#

Or add this manually:

[tool.uv.sources]
dagger-io = { path = "sdk", editable = true }