Skip to content

fix: release workspace locks held by duplicate descriptors - #15

Merged
adamcavendish merged 2 commits into
mainfrom
adamcavendish/fix-workspace-lock-release
Oct 12, 2026
Merged

adamcavendish merged 2 commits into
mainfrom
adamcavendish/fix-workspace-lock-release

Conversation

@adamcavendish

Copy link
Copy Markdown
Contributor

Summary

  • Release the workspace lock explicitly when the last Workspace owner drops.
  • Prevent duplicated or inherited lock descriptors from keeping Registry::open blocked after shutdown and owner release.
  • Add a Unix regression test that duplicates the lock descriptor, drops the workspace, and verifies the same workspace can be reopened.

The crate version remains 0.0.1; this PR does not publish a new crate release.

Verification

  • cargo test --locked passed; all non-ignored tests passed.
  • cargo build --locked passed.
  • cargo clippy --locked --all-targets -- -D warnings passed.
  • cargo fmt --all -- --check passed.
  • git diff --check passed.

Documentation

  • Added an Unreleased CHANGELOG entry describing the workspace lock lifecycle fix.
  • README and Registry/HTTP lifecycle documentation remain accurate and require no changes.

@adamcavendish
adamcavendish merged commit 213e852 into main Oct 12, 2026
11 checks passed
@adamcavendish
adamcavendish deleted the adamcavendish/fix-workspace-lock-release branch October 12, 2026 08:09
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