flowey: Fix running multi-step pipelines locally on windows#2604
Merged
smalis-msft merged 1 commit intomicrosoft:mainfrom Jan 1, 2026
Merged
flowey: Fix running multi-step pipelines locally on windows#2604smalis-msft merged 1 commit intomicrosoft:mainfrom
smalis-msft merged 1 commit intomicrosoft:mainfrom
Conversation
benhillis
approved these changes
Dec 31, 2025
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
3 participants
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 running a pipeline locally, flowey will create temporary working directories for each step and move the process's working directory into them. Later on, flowey may try to delete these temporary directories. This is fine on Linux, but on Windows processes hold a handle to their working directory, so this fails. Fix this by just leaving the last step's working directory after it's done.