#[solved] this should work, but failing mounting the requested directory

1 messages · Page 1 of 1 (latest)

proper jolt
#

this is the error:

# 
% dagger call \
 --name my-test \
  new-interlink \
    --manifests ./manifests \
  test stdout
✔ connect 1.3s
✔ initialize 4.4s
✔ prepare 0.4s
✔ interlink(name: "my-test"): Interlink! 0.3s
✘ Interlink.newInterlink(
    manifests: ✔ ModuleSource.resolveDirectoryFromCaller(path: "./manifests"): Directory! 0.0s
  ): Interlink! 0.1s
! call function "NewInterlink": process "/runtime" did not complete successfully: exit code: 2

Full t*race at https://dagger.cloud/INFN/traces/4e30dbf4f72366463dafe1ea72e00040

Error: response from query: input: interlink.newInterlink resolve: call function "NewInterlink": process "/runtime" did not complete successfully: exit code: 2

Stderr:
panic: unexpected nil pointer for argument "source"
📎 message.txt
#

any clue? anyone with similar issue?

hasty phoenix
#

is m.Registry set?

#

ah, pluginEndpoint is nil

#

you can't currently pass nil values to any dagger functions

#

when you don't specify the arg it's nil

#

but yes, this is weird, we should fix this

proper jolt
#

nvm.... yeah, I missed one piece of code while migrating... a bit misleading error, but definetly my fault