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

Print error code if run fails #2848

Merged
merged 1 commit into from
Oct 18, 2023
Merged

Print error code if run fails #2848

merged 1 commit into from
Oct 18, 2023

Conversation

jonashaag
Copy link
Collaborator

No description provided.

Copy link
Member

@AntoinePrv AntoinePrv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually I am wondering if it's a good idea to modify the output of the subprocess.
Then it becomes difficult to parse the output for user, i.e. micromamba run cmd is not longer a substitute for simply running cmd.

I think we should do whatever bash -c <cmd> is doing, which I believe is stdout > stdout, stderr > stderr and same return code.

@jonashaag
Copy link
Collaborator Author

But this about errors in Mamba, not in the subprocess, no? If bash fails to start a process, or a process segfaults or whatever, it prints stuff.

Copy link
Member

@AntoinePrv AntoinePrv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But this about errors in Mamba, not in the subprocess, no?

I think you're right

@AntoinePrv AntoinePrv merged commit e63fe80 into main Oct 18, 2023
23 checks passed
@AntoinePrv AntoinePrv deleted the issue-2771 branch October 18, 2023 09:00
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.

None yet

2 participants