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

[code2fn] - Gromet pipeline changing current working directory #596

Closed
vincentraymond-ua opened this issue Oct 26, 2023 · 3 comments
Closed
Assignees
Labels
bug Something isn't working Code2FN

Comments

@vincentraymond-ua
Copy link
Contributor

During the Gromet pipeline, the cwd is changed multiple times. Normally, the cwd is changed back once Gromet is generated. However, if the Gromet pipeline fails and the exception is caught, the cwd is never changed back. This causes unexpected behavior and depending on where the pipeline failed and where the script was originally run from, the cwd can be completely different.

This makes writing scripts like the model_coverage_report more complicated as you have to assume that the cwd has been changed and change it back before/after every step.

@vincentraymond-ua
Copy link
Contributor Author

Need to look in to where the Gromet pipeline is changing the cwd.

@myedibleenso myedibleenso added this to the [DARPA] Milestone 11 milestone Nov 15, 2023
@titomeister
Copy link
Contributor

@vincentraymond-ua Was this resolved or is this still ongoing?

@vincentraymond-ua
Copy link
Contributor Author

Yes, this is resolved, I'll go ahead and close it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Code2FN
Projects
None yet
Development

No branches or pull requests

3 participants