Details
-
Type:
Bug
-
Status: Open
-
Priority:
(None)
-
Resolution: Unresolved
-
Affects Version/s: 3.18.0
-
Fix Version/s: None
-
Component/s: cf-agent, Promise type: files
-
Labels:None
Description
A user emailed me directly:
I have changed the hashing to "md5" from "best" and that has done away with the double change detection.
As far as reproducing, you should be able to make a change detection file promise on a directory using "best" hashing and observe that changes are detected twice on subsequent runs of the agent. Changing to md5 hashing fixes the issue for me, btw I am using "content" only for changes detection.