Skip to content

fix: atomically refresh resource lock heartbeats#100

Merged
V3RON merged 1 commit intomainfrom
fix/resource-lock-failure
Apr 7, 2026
Merged

fix: atomically refresh resource lock heartbeats#100
V3RON merged 1 commit intomainfrom
fix/resource-lock-failure

Conversation

@V3RON
Copy link
Copy Markdown
Contributor

@V3RON V3RON commented Apr 7, 2026

Summary

  • atomically replace owner.json during resource lock heartbeat refreshes so readers never observe truncated JSON
  • skip overlapping heartbeat ticks in the same process to avoid self-races while a prior refresh is still in flight
  • add a regression test that delays heartbeat writes and verifies owner metadata remains readable across repeated refreshes

Testing

  • pnpm vitest run packages/jest/src/__tests__/resource-lock.test.ts
  • pnpm vitest run --project @react-native-harness/jest

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 7, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
react-native-harness Ready Ready Preview, Comment Apr 7, 2026 10:29am

Request Review

@V3RON V3RON merged commit 9e114a6 into main Apr 7, 2026
6 checks passed
@V3RON V3RON deleted the fix/resource-lock-failure branch April 7, 2026 15:48
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