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

Detect files not touched? #3

Open
PeterJCLaw opened this issue Sep 16, 2023 · 0 comments
Open

Detect files not touched? #3

PeterJCLaw opened this issue Sep 16, 2023 · 0 comments

Comments

@PeterJCLaw
Copy link
Owner

Currently if the command completes successfully but does not actually touch the output files then this is not detected. However in many cases this could indicate an error -- either that the wrong files are being checked or that the command is doing the wrong thing.

One option might be to delete the files however that seems undesirable, at least as a default. A better option might be to stat the files and ensure that their modification times have increased. That is likely to handle most cases. Letting users opt out of that check also seems useful -- for cases where the underlying command has its own idempotency checks.

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

1 participant