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

Additional options for hashing-strategy #1843

Closed
meganshand opened this issue Jan 11, 2017 · 3 comments
Closed

Additional options for hashing-strategy #1843

meganshand opened this issue Jan 11, 2017 · 3 comments

Comments

@meganshand
Copy link

It would be great to be able to include last modified date in the hashing-strategy when using the current path strategy. This would prevent having incorrect output from a task if the file was modified but the path was not.

@katevoss
Copy link

@geoffjentry how much effort would it be to include the last modified date in the hash?
@meganshand do you still want this feature? Or have you found a workaround?

@meganshand
Copy link
Author

meganshand commented Sep 19, 2017

I'm still interested in this feature in the sense that it will prevent mistakes in the future, but it is not blocking any of my work. It's more of a QC feature. If it isn't easy I personally wouldn't make it a high priority.

@geoffjentry geoffjentry added the Needs Triage Ticket needs further investigation and refinement prior to moving to milestones label Feb 21, 2019
@geoffjentry geoffjentry removed the Needs Triage Ticket needs further investigation and refinement prior to moving to milestones label Aug 8, 2019
@geoffjentry
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants