Skip to content

feat(watcher): debounce FS watchers #1374

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

Conversation

alex-courtis
Copy link
Member

@alex-courtis alex-courtis commented Jun 26, 2022

requires #1373

Not very useful until we move to fs_event as fs_poll is aready throttled.

I have played around a few options but was not happy:

  1. Abandon refresh when there is a refresh in progress for that directory - can miss actual changes
  2. Queue one refresh when there is one in progress - can result in two refreshes, which will be a big problem when we move to real time FS events

Debounce refreshes by absolute path seems the best option.
Having multiple refresh events running for different paths is OK, as we are only looking at the FS and git for that path.

@alex-courtis alex-courtis changed the base branch from master to feat/optimise-watchers-1-partial-git-refresh June 26, 2022 06:45
@alex-courtis alex-courtis requested a review from kyazdani42 June 26, 2022 07:04
@alex-courtis alex-courtis merged commit 868111f into feat/optimise-watchers-1-partial-git-refresh Jun 28, 2022
@alex-courtis
Copy link
Member Author

Whoops... merged to feat/optimise-watchers-1-partial-git-refresh

Manually rebased / merged to master.

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

Successfully merging this pull request may close these issues.

2 participants