dagger/dagger · error
failed to load module dependencies: %w
Error message
failed to load module dependencies: %w
What it means
The errgroup Wait after concurrently selecting `asModule` on each toolchain source failed; the wrapped error is whichever per-toolchain load failed (arg building via BuildLegacyAsModuleArgs or the dagql select itself). This is an aggregate wrapper — the real cause is inside.
Source
Thrown at core/schema/modulesource.go:4364
nameOverride,
false, // related modules never set LegacyDefaultPath (see pendingRelatedModule)
dpRef,
dpPin,
configDefaults,
false, // DefaultsFromDotEnv is not set for related modules
argCustomizations,
)
if err != nil {
return fmt.Errorf("build toolchain asModule args: %w", err)
}
return dag.Select(ctx, tcSrc, &tcMods[i],
dagql.Selector{Field: "asModule", Args: toolchainAsModuleArgs},
)
})
}
if err := eg.Wait(); err != nil {
return nil, fmt.Errorf("failed to load module dependencies: %w", err)
}
deps, err := s.loadDefaultSchemaBuilder(ctx, src)
if err != nil {
return nil, err
}
for _, depMod := range depMods {
deps = deps.Append(core.NewUserMod(depMod))
}
return deps, nil
}
// loadDefaultSchemaBuilder returns a SchemaBuilder seeded with only the default
// (core) dependencies, with the core module pinned to src's engine version
// view. Callers append the user modules they want to expose.
func (s *moduleSourceSchema) loadDefaultSchemaBuilder(
ctx context.Context,View on GitHub (pinned to 82ba2681db)
Solutions
- Look at the wrapped underlying error to identify the failing toolchain
- Verify each toolchain/related module source is loadable as a module
- Retry after fixing the failing dependency's source/config
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at core/schema/modulesource.go:4364 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of dagger/dagger@82ba2681db (2026-09-05).
Data as JSON: /api/errors/029257e9ddcd4c9c.
Report an issue: GitHub.