Normalize command-line argument paths #14934
Merged
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
In particular, this fixes an issue on Windows where some functions will misbehave if forward slashes are provided rather than double backslashes.
catboxanon
changed the title
AUTOMATIC1111
approved these changes
Feb 17, 2024
Closed
6 tasks
4 tasks
Closed
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.
Description
This aims to fix an issue on Windows where some functions will misbehave if forward slashes are provided rather than double backslashes. An example of this is the current tree generation procedure implemented in #14588, which produces no tree if a path with forward slashes
X:/like/thisis provided via the cmd line arg rather than backslashesX:\\like\\this.This would partially resolve the issue being experienced here: lllyasviel/stable-diffusion-webui-forge#121
Checklist: