fix: atomically replace route metadata during sync - #17096
Draft
svelte-triage-bot[bot] wants to merge 1 commit into
Draft
fix: atomically replace route metadata during sync#17096svelte-triage-bot[bot] wants to merge 1 commit into
svelte-triage-bot[bot] wants to merge 1 commit into
Conversation
|
Install the latest version of pnpm add https://pkg.svelte.dev/@sveltejs/kit/c/f87a22d80aea6de76eb77dd5cf4727efb9db300aOpen in Note This PR is from a fork. A maintainer must approve approve each commit before it can be built and installed. |
🦋 Changeset detectedLatest commit: f87a22d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #17095.
Concurrent syncs could read
route_meta_data.jsonwhile another process had truncated it for a direct rewrite. This caused intermittentJSON.parsefailures.This change:
finallyblockThe unique temporary name avoids collisions, while its location prevents another concurrent sync's types cleanup from removing an in-progress write.
Verification:
write_types/index.spec.jssuite (21 tests)pnpm -F @sveltejs/kit test:unit(783 passed)pnpm lintpnpm checkpnpm -F @sveltejs/kit prepublishOnlysvelte-kit syncprocesses (0 failures)