Repository navigation
fix: avoid duplicate restoration of explicit directory markers - #330
Open
jacksonriding wants to merge 1 commit into
Open
jacksonriding wants to merge 1 commit into
jacksonriding wants to merge 1 commit into
Conversation
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.
When LibreChat attaches a directory marker under a renamed display filename, the normalized object listing can return the same stored
.dirkeepagain under its original name. The sandbox then downloads both references to the stored path and rejects execution.Suppress the extra listing entry by object ID within the listed session. Explicit downloads still preserve marker contents, and an identical object ID in another session does not suppress an inherited marker.
Validation on Bun 1.4.2: