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

triger the propagator from the command line scanner #24256

Merged
merged 1 commit into from
Apr 26, 2016

Conversation

icewind1991
Copy link
Contributor

Fixes #24255

cc @PVince81

@icewind1991 icewind1991 added this to the 9.1-current milestone Apr 25, 2016
@mention-bot
Copy link

By analyzing the blame information on this pull request, we identified @LukasReschke, @DeepDiver1975 and @nickvergessen to be potential reviewers

@@ -168,5 +180,9 @@ public function scan($dir = '') {
}
}
}

private function triggerPropagator(IStorage $storage, $internalPath) {
$storage->getPropagator()->propagateChange($internalPath, time());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@icewind1991 can you remind me whether this is debounced on the path ?

Because if we detect several changes within the same folder, it would be expensive to propagate the etag to the parents several times for every found file.

@PVince81
Copy link
Contributor

Tested, works 👍

@karlitschek backport to 9.0.2 ?

@karlitschek
Copy link
Contributor

great. please backport

@PVince81
Copy link
Contributor

@icewind1991 please submit the backport PR, thanks

@icewind1991
Copy link
Contributor Author

stable9: #24261

@MorrisJobke
Copy link
Contributor

👍

@MorrisJobke MorrisJobke merged commit 23e7ad7 into master Apr 26, 2016
@MorrisJobke MorrisJobke deleted the scanner-propagate branch April 26, 2016 08:05
@lock
Copy link

lock bot commented Aug 6, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Scanner doesn't propagate etags any more when file changed
5 participants