Skip to content

CoreUtils HashAlgorithm aborts, if 1 input of several does'nt exist #7906

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

Open
Somebody111de opened this issue May 9, 2025 · 1 comment · May be fixed by #7918
Open

CoreUtils HashAlgorithm aborts, if 1 input of several does'nt exist #7906

Somebody111de opened this issue May 9, 2025 · 1 comment · May be fixed by #7918

Comments

@Somebody111de
Copy link

Hello,

when called with multiple inputs, CoreUtils aborts, if 1 input does'nt exist.

Example:

CoreUtils sha256sum *.7z *.zip *.rar *.rev

  • If *.7z does'nt exist, but another, CoreUtils makes Error-Message and aborts.

  • If .7z+.rar exist and *.zip does'nt exist, *.7z is processed and the rest not; CoreUtils makes Error-Message and aborts after *.zip.

Could this be changed, so that it doesn't abort, but just displays an Error-Message and the rest is still processed?

Affects not only sha256sum, but all hash algorithms.

This worked in earlier versions of GNU-CoreUtils (e.g. v6.9). In newer versions of GNU-CoreUtils (v8.32/v9.70), it no longer works either.

I realize, the problem can be avoided with a FOR loop, but it would be easier and faster without it.

Thanks for your good compilation and have a nice day.

Greatings

@Cuteness-overload
Copy link

The goal of this project is to replicate the behaviour of GNU-CoreUtils.
As stated in the README.md Differences with GNU are treated as bugs.

As such, if this is the behaviour of GNU-CoreUtils, then this is not an issue.

@Qelxiros Qelxiros linked a pull request May 11, 2025 that will close this issue
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 a pull request may close this issue.

2 participants