IntersectMBO / IntersectMBO/cardano-haskell-packages

Add check that latest index state is not in the future

Open
#216 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
36
Forks
35
Avg merge
1d 4h
Merged PRs (30d)
25

Description

If someone adds a package that is in the future, as happened recently (discussion here: https://github.com/input-output-hk/cardano-haskell-packages/pull/214), then we will accept that fine. The only problem with this is:
1. To use it you have to put your index-state in the future
2. Subsequent people adding packages will have to add timestamps _after this future date_. This does not play well with all our scripts which assume they can safely put in the current time as the timestamp, they will all not work until the future date passes.

This is a bit of a weird occurrence, but annoying enough that we should probably guard against it.

Contributor guide

Open the contributing guide

Research direction

No file or test is named in the issue; begin by locating the scripts that validate or update the latest index state. Done means an index state later than the current time is rejected while existing package-addition workflows remain valid.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
build-system
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.