fixed duplicate attachments on dump on windows (#28019) #28031
Merged
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.
Backport #28019 by @anudeepreddy
Hi,
This PR fixes #27988. The use of
path.join
(which uses/
as the file separator) to construct paths and comparing them with paths constructed usingfilepath.join
(which uses platform specific file separator) is the root cause of this issue.The desired behavior is to ignore attachments when dumping data directory. Due to the what's mentioned above, the function
addRecursiveExclude
is not actually ignoring the attachments directory and is being written to the archive. The attachment directory is again added to the archive (with different file separator as mentioned in the issue) causing a duplicate entry on windows.The solution is to use
filepath.join
inaddResursiveExclude
to constructcurrentAbsPath
.