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

'reprocess all' is confusing #129

Closed
takluyver opened this issue Nov 9, 2023 · 2 comments
Closed

'reprocess all' is confusing #129

takluyver opened this issue Nov 9, 2023 · 2 comments

Comments

@takluyver
Copy link
Member

FXE just got bitten by this: they set up DAMNIT for a proposal which already has runs, and then ran amore-proto reprocess all, expecting it to process all the existing runs. Reprocessing specific run numbers can add them, but all only means all the runs DAMNIT already knows about, which in this case is 0 runs.

Workaround: specify the run numbers, e.g. amore-proto reprocess $(seq 2 77)

An easy improvement would be a 'did you mean' message when there are 0 runs. Going further, we might consider turning reprocess into process, where all would logically mean 'all the runs in the proposal'. We could add ways to reprocess all the runs already in DAMNIT, or to only process runs not already in DAMNIT.

@JamesWrigley
Copy link
Member

Possible duplicate: #87

@takluyver
Copy link
Member Author

D'oh. Yes, that's basically the same. Should have searched before I wrote this. Thanks!

@takluyver takluyver closed this as not planned Won't fix, can't repro, duplicate, stale Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants