Friendlier --read-data-subset checks

[fede]

@MichaelEischer

Anything more flexible than the initial --read-data-subset=daily/weekly suggestion would require some way to track state which is too much work for now.

Understood. Thank you very much for answering.

[MichaelEischer]

@damoclark

Am I right that the overhead in making a change to the repository is quite high (i.e. making change, new tests, user migration tools, documentation etc), and it is not worth all that overhead for what is proposed?

A proper way to store state information about the last check would require introducing a new file type which requires a lot of changes in quite a few places. Doing that in a way that just allows storing check state feels too much work, so we’d need something more generic, which in turn requires further planning. So a major part of the work would actually be coming up with the design. This requires a lot of thought as we’re pretty much stuck with it once it’s released.

@damoclark

If so, could this be something that is added to a low priority list, that could be rolled into the next repository change for something more substantial?

Issue tracking happens on Github, so feel free to open an issue there. There’s not special low priority list. In fact, the suggest change is substantial enough that it would warrant a separate repository version change.