gastownhall/beads · error

resolving %s: %w

Error message

resolving %s: %w

What it means

Error "resolving %s: %w" thrown in gastownhall/beads.

Source

Thrown at cmd/bd/comments_proxied_server.go:160

	return result.Comment, issue, nil
}

// resolveCommentTargetProxied resolves the anchor and applies the CLI's own
// pre-flight policy. It reads in a unit of work of its own and writes nothing,
// so the role's request stays the whole of the transaction.
func resolveCommentTargetProxied(ctx context.Context, id string) (*types.Issue, error) {
	uw, err := proxiedOpenReadUOW(ctx)
	if err != nil {
		return nil, err
	}
	defer uw.Close(ctx)

	issue, _, err := workapi.GetIssueOrWisp(ctx, workapi.NewUOWDetailSource(uw), id)
	if errors.Is(err, storage.ErrNotFound) {
		return nil, fmt.Errorf("issue %s not found", id)
	}
	if err != nil {
		return nil, fmt.Errorf("resolving %s: %w", id, err)
	}
	if err := validateIssueUpdatable(id, issue); err != nil {
		return nil, err
	}
	return issue, nil
}

View on GitHub (pinned to 71377f2769)

Solutions

1. Check the wrapped resolution error for its cause
2. Correct the identifier or state problem and retry the resolve

bd show "$ID" >/dev/null 2>&1 || exit 1  # cheap pre-check before comment resolve

if ! bd comment "$ID" --text "$T" 2>err.txt; then
  grep -q 'resolving' err.txt && bd doctor  # store-level failure, not just missing ID
fi

When it happens

Trigger: Thrown at cmd/bd/comments_proxied_server.go:160 when the library encounters an invalid state.

Common situations: See trigger scenarios.

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