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

date should return error status on unparseable date #4525

Closed
dfandrich opened this issue Mar 17, 2023 · 1 comment · Fixed by #4526
Closed

date should return error status on unparseable date #4525

dfandrich opened this issue Mar 17, 2023 · 1 comment · Fixed by #4526
Labels

Comments

@dfandrich
Copy link

This invocation should return an error status and not the But it failed! message, but that's not what it does (on 0.0.17 on Alpine x86_64):

~ # uutils-date -d foo && echo But it failed!
uutils-date: invalid date 'foo'
But it failed!

date should return an error status when the -d string can't be parsed, just like GNU coreutils, Busybox, FreeBSD and Solaris already do.

@tertsdiepraam
Copy link
Member

Thanks! Seems like we were returning 1 in a lot of other cases, but missed this one :)

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

Successfully merging a pull request may close this issue.

3 participants