Repository navigation
fix(solve): give each generated stack policy its own file - #32
Merged
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
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.
Each generated stack policy is now its own file.
eb-stack-policy-<toolchain>-<pid>.jsonfor every solve in the process and left the file behind. Both the CLI and the MCP server now create a new empty file whose name is not a function of the process id alone, and the MCP server removes the file it created when the solve returns.exclusive_temp_paths_are_distinct_fileswrites two policies in one process and checks they are not the old predictable path. The commit has a towncrier fragment.