uutils / uutils/coreutils

bug(date): Ignore next when a full date provided instead of trying Next against the date

Open
#14,681 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

U - date
Dominant language
Rust
Stars
24.1k
Forks
2k
Avg merge
1d 5h
Merged PRs (30d)
365

Description

Hi, uutils mainteners

we saw that when trying

relunsec@relunsec:~/software/coreutils/target/debug$ ./date  -d "Next Friday Sep 25 12:00:00 AM EDT 2026"
Fri Oct  2 12:00:00 AM EDT 2026
relunsec@relunsec:~/software/coreutils/target/debug$ gnudate  -d "Next Friday Sep 25 12:00:00 AM EDT 2026"
Fri Sep 25 12:00:00 AM EDT 2026
relunsec@relunsec:~/software/coreutils/target/debug$ 

same with

relunsec@relunsec:~/software/coreutils/target/debug$ ./date  -d "Next Sunday Sep 25 12:00:00 AM EDT 2026"
Sun Sep 27 12:00:00 AM EDT 2026
relunsec@relunsec:~/software/coreutils/target/debug$ gnudate  -d "Next Sunday Sep 25 12:00:00 AM EDT 2026"
Fri Sep 25 12:00:00 AM EDT 2026

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the two date -d examples and compare their output with GNU date, then trace the date command's handling of Next together with a full date. Done means both inputs produce the GNU-compatible dates shown in the issue, with the full date taking precedence where appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.