gastownhall/beads · error

failed to load dependencies: %w

Error message

failed to load dependencies: %w

What it means

Wraps an error from UnitOfWork.DependencyUseCase().GetIssueDependencyRecords while assembling dependency edges for the graph. Called after issues are collected, using all issue IDs. The wrapped cause identifies why the dependency lookup failed.

Source

Thrown at cmd/bd/graph_proxied_server.go:130

			return nil, fmt.Errorf("failed to search issues: %w", err)
		}
		allIssues = append(allIssues, page.Items...)
	}

	if len(allIssues) == 0 {
		return nil, nil
	}

	issueMap := make(map[string]*types.Issue, len(allIssues))
	ids := make([]string, 0, len(allIssues))
	for _, issue := range allIssues {
		issueMap[issue.ID] = issue
		ids = append(ids, issue.ID)
	}

	recs, err := uw.DependencyUseCase().GetIssueDependencyRecords(ctx, ids)
	if err != nil {
		return nil, fmt.Errorf("failed to load dependencies: %w", err)
	}
	var allDeps []*types.Dependency
	for _, issue := range allIssues {
		for _, dep := range recs[issue.ID] {
			if _, ok := issueMap[dep.DependsOnID]; ok {
				allDeps = append(allDeps, dep)
			}
		}
	}

	return assembleAllSubgraphs(allIssues, issueMap, allDeps), nil
}

View on GitHub (pinned to 71377f2769)

Solutions

1. Check the wrapped cause for the storage-level failure and address it (connectivity, corruption, migration).
2. Verify the dependencies table exists and is queryable in the Dolt database.
3. Retry; if it fails only with large issue counts, reduce scope or upgrade bd for batched dependency loading.

if len(ids) == 0 { return nil, nil } // skip dependency query when no issues

recs, err := uw.DependencyUseCase().GetIssueDependencyRecords(ctx, ids)
if err != nil {
	return nil, fmt.Errorf("failed to load dependencies: %w", err)
}

When it happens

Trigger: loadAllGraphSubgraphsUOW calls GetIssueDependencyRecords(ctx, ids) with every loaded issue ID; any non-nil error from the dependency use case/storage layer is wrapped as this error.

Common situations: Missing or corrupted dependencies table, storage driver disconnection mid-request, very large ID list exceeding query limits, or schema version drift between bd and the database.

Related errors

• failed to search issues: %w
• no store is open for this workspace
• failed to check parent issue: %w
• load dependency records: %w
• resolving %s: %w

AI-assisted analysis of gastownhall/beads@71377f2769 (2026-08-30). Data as JSON: /api/errors/61f239d3ac87610c. Report an issue: GitHub.