Development record
A drain reserves an issue with the path its found_at names, and when that path is a tracked directory the drain shows no directory warning anywhere: reserveKey builds the drain's hold without the claim result's Directories (internal/core/implement/loop/reservation.go around line 603), and the drain's text and --json renderings never print its start's reservation warnings. The build and reserve verbs warn of a directory footprint; the drain leaves it unsaid, by design so far because a drain narrows each lane to the files it changed once it reaches its landing, but until then the directory holds off every other reservation inside it, unannounced.
A drain reserves an issue with the path its found_at names, and when that path is a tracked directory the drain shows no directory warning anywhere: reserveKey builds the drain's hold without the claim result's Directories (internal/core/implement/loop/reservation.go around line 603), and the drain's text and --json renderings never print its start's reservation warnings. The build and reserve verbs warn of a directory footprint; the drain leaves it unsaid, by design so far because a drain narrows each lane to the files it changed once it reaches its landing, but until then the directory holds off every other reservation inside it, unannounced.
Frontmatter
| id | iss-2610230855093864 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610230855093864-a-drain-reserves-a-directory-found-at.md
open on GitHub ↗ · commit history ↗