Fix chunk symlinks to ensure overwriting old links #3868
Merged
Conversation
This file contains 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
nicknytko
approved these changes
Feb 23, 2021
Yep, I tested it because I no longer trust anything 😄 |
|
Successfully tested on staging. |
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.
The
ensureSymlink()function silently does nothing if the destination already exists, even if it isn't the correct symlink (see jprichardson/node-fs-extra#786, jprichardson/node-fs-extra#869, jprichardson/node-fs-extra#826). This means that with the new symlink chunk code (see #3354) we will never update a question chunk, even when there is a new version of the question available. To work around this we create the link with a temporary name and move it to the correct link name.