Represent label resolution states in request snapshots #28

New issue

Open

opened 2026-09-21 01:14:21 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-09-21 01:14:21 +00:00

Owner

Original issue: source #29
Original author: barrettruth
Original date: 2026-08-31T06:09:41Z

Represent why a label can or cannot resolve in the immutable index captured by a request. The model must distinguish at least:

a resolved source or evaluated target;
a proven missing target;
an unavailable or unfinished graph;
an unfetched apparent repository;
an unknown repository mapping;
a target pattern that names a set rather than one target.

Derive states from the existing static, evaluated, and repository tiers. Do not add a parallel readiness flag or invoke Bazel from a handler.

> Original issue: source #29 > Original author: `barrettruth` > Original date: 2026-08-31T06:09:41Z Represent why a label can or cannot resolve in the immutable index captured by a request. The model must distinguish at least: - a resolved source or evaluated target; - a proven missing target; - an unavailable or unfinished graph; - an unfetched apparent repository; - an unknown repository mapping; - a target pattern that names a set rather than one target. Derive states from the existing static, evaluated, and repository tiers. Do not add a parallel readiness flag or invoke Bazel from a handler.

barrettruth added the

area:starlark

enhancement

labels

2026-09-21 01:14:21 +00:00