🐛 Fix FragPipe parameter parsing #302
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
added 2 commits
May 19, 2024 17:43
- windows path in fragpipe_win_path.workflow correctly interpreted on Windows, but will probably fail on UNIX servers...
- maps both Posix and Windows path correctly: https://stackoverflow.com/a/73682980
enryH
force-pushed
the
fragpipe_parse_win_path_on_unix
branch
from
0e3a3a0 to
4c21757
Compare
mlocardpaulet
approved these changes
May 24, 2024
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.
Windows path in fragpipe_win_path.workflow correctly interpreted on Windows, but will probably fail on UNIX servers...
Start with adding a new test.
Solve issue #285