Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While trying to fix #3303 i noticed that my file monitor had stale caches.
I deleted a file long time, but it was still present in
Cache/Data/Flow_Monitor/Flow_ClassFiles_filesAndModificationTimes
.That should not be the case as it should have been flushed. Maybe the file monitor even noticed the change and other parts of flow were aware of it but just the deletion in the file didnt work.
Either way it seems to be flaky and expensive to have two caches with similar data.
This change in theorie makes the
Flow_ClassFiles_directoriesAndFiles
cache obsolete by introducing a new method to that on theModificationTimeStrategy
.The idea was, if i loop already through all the folders we can just diff it to the previously saved modification stamps and see whats left and check for file existence.
That seems to work well. And in one hickup in flow, that i could not further reproduce, even better than the current strategy which didnt detect a removal.
to test i just dumped a bit around ;D
TODOS;