Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix regression in how we handle solution copying #570

Merged
merged 2 commits into from
Jun 8, 2023

Conversation

ozgurakgun
Copy link
Collaborator

Fix regression in how we handle solution copying. This only effected parameter files that had dashes (-) in the filename. Added a regression test case as well. Thanks @ott2 for reporting!

…parameter files that had dashes (-) in the filename. Added a regression test case as well. Thanks @ott2 for reporting!
@ozgurakgun
Copy link
Collaborator Author

This seems to work now @ott2. I'll merge soon, but feel free to take a look at the diff before I do so? I might be missing something again...

@ozgurakgun ozgurakgun merged commit 40ae1e2 into main Jun 8, 2023
@ozgurakgun ozgurakgun deleted the fix-solution-copy-regression branch June 8, 2023 13:51
@ott2
Copy link
Collaborator

ott2 commented Jun 26, 2023

@ozgurakgun Not sure this is the precise same issue, but current head has this solution copying problem if one specifies a pathname for a parameter file that includes a directory separator:
conjure solve tmp/test.essence tmp/test.param
fails to copy the solution file, whereas conjure solve tmp/test1.essence works fine, with an unparameterised spec.

Edit: in case this has a different cause, have opened a new issue #578 about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants