-
Notifications
You must be signed in to change notification settings - Fork 547
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
"Initialization" Output Returned as Stdout #5003
Comments
Does the |
we will fix this @BoweFlex |
No, this output is returned either way. I didn't realize the flag was already included, it must not be working as expected. Thanks @harshavardhana |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The first time that any mc command is run, the following output is given:
Because of this, some situations cannot be automated properly due to this being returned when retrieving stdout from a command that just happens to be the first execution of mc (i.e. putting the output of an
mc cat
command into a variable. This is especially problematic with something like running an automated job pushing data through mc on a docker container with environment variables to control MC access.Expected behavior
I think there are a few potential fixes, but without looking more I'm not positive what makes the most sense for this project:
mc init
command, to create this configuration without any other expected output.Actual behavior
When run for the first time, or after removing config (i.e.
rm -rf /root/.mc
):Results are the same with something like:
Steps to reproduce the behavior
Start docker container w/ mc installed, and/or remove /root/.mc, and try running an mc command.
mc --version
Confirmed on both:
System information
Tested on rocky linux 9
The text was updated successfully, but these errors were encountered: