Diagnosing Dream Builds

When to use

• Just ran dream inject push-all / push-specific, but tau query builds --since 1h shows nothing.
• Need raw job ids that tau isn't surfacing.
• A build looks failed but tau won't print its logs.
• Verifying that a push-specific actually enqueued a job before chasing other failure causes.

Mental model

tau list/query builds is a convenience view. On Dream local clouds it isn't always wired to local jobs. The source of truth for Dream jobs is the local jobs HTTP endpoint exposed by Dream's auth/seer service. Once you have a job id from there, tau query logs --jid <jid> can download the logs.

Token health: if GET /jobs/<project_id> (or related Patrick HTTP) returns 401 or invalid Github token, refresh the GitHub PAT in ~/tau.yaml / tau login … first — see authenticating-taubyte-cli. A stale token looks like a "Dream is broken" problem but is only auth.

Workflow