Skip to content

Keep landing ownership records in the knit home (knit) - #260

Merged
marc-merino merged 1 commit into
mainfrom
knit/keep-landing-ownership-records-in-the-knit-home
Oct 12, 2026
Merged

marc-merino merged 1 commit into
mainfrom
knit/keep-landing-ownership-records-in-the-knit-home

Conversation

@marc-merino

@marc-merino marc-merino commented Oct 12, 2026 •

Copy link
Copy Markdown
Collaborator

Knit Bundle

View bundle

This PR is part of Knit bundle keep-landing-ownership-records-in-the-knit-home.

See the other review objects in this bundle:

Bundle id: keep-landing-ownership-records-in-the-knit-home
Bundle title: Keep landing ownership records in the knit home

Local landing locks and each project's latest-run generation lived in the OS
temp directory. Temp cleanup could silently drop a lock meant to survive a
crash, or the record that a previous landing left unresolved effects, and on
Linux the first user to land owned /tmp/knit-landing-ownership, so every other
user on the machine failed with a misleading "landing resource is owned".

They now live in landing-ownership/ next to the user-level config (KNIT_HOME,
XDG_CONFIG_HOME/knit or ~/.config/knit). Records an earlier release left in the
temp directory still block, so an upgrade never skips an in-flight landing or
an unresolved generation. Unit tests keep a temp directory so they never write
into a developer's real config.

The test harness now gives every test its own knit home, which isolates the
locks per test; the per-workspace temp directories added for the same purpose
are removed.

Knit-Group: kg_20261012_e3ecdd
Knit-Bundle: keep-landing-ownership-records-in-the-knit-home
@marc-merino
marc-merino merged commit f25577f into main Oct 12, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant