Accept more ISO8601 timestamp formats

Open
#12,630 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
66/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
haskell
Domain
build-system

Research direction

Start at cabal-install/src/Distribution/Client/IndexUtils/Timestamp.hs around lines 94-100, where the TODO sits and the existing parser handles @unix, full ISO8601 UTC and HEAD; read that parser and its error message closely before changing anything. Add the three forms listed (date-only as UTC midnight, minutes without seconds, numeric UTC offset) and extend the surrounding test module with one case per accepted form plus a rejection case. Done looks like --index-state=2026-06-01 and the other two examples parsing while local-time inputs still error.

Written by the indexing model from the issue text.

Description

needs triage type: enhancement

https://github.com/haskell/cabal/blob/0fd9ad9bd211a15033094b3a787765fa0af6e52f/cabal-install/src/Distribution/Client/IndexUtils/Timestamp.hs#L94-L100

I'd rather write just the shorter YYYY-MM-DD form of the timestamp, if that works so I'm promoting the above TODO note to a feature enhancement issue.

The behaviour at the moment is to get an error (with minor grammar glitches):

Error: cabal: invalid argument to option `--index-state': index-state must be
a unix-timestamps (e.g. '@1474732068'), a ISO8601 UTC timestamp (e.g.
'2016-09-24T17:47:48Z'), or 'HEAD'

I don't think we need a whole lot more forms of ISO8601 but a few that are more convenient. Anything that would parse to a local time we need to be wary of.

  1. A date on its own, 2026-06-01, meaning the start of that day in UTC.
  2. A time without seconds, 2026-06-01T12:30Z (from the TODO).
  3. A numeric UTC offset, 2026-06-01T12:00:00+12:00 (from the TODO).
Dominant language
Haskell
Stars
1.8k
Forks
766
Avg merge
5d 21h
Merged PRs (30d)
27

Getting set up

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.

More from haskell/cabal

All issues in haskell/cabal

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.