Fix typo in comment about fsnotify behavior
Correct loose (opposite of tight) to lose (opposite of keep).
This commit is contained in:
parent
0f12e414a6
commit
414d3bbbd8
1 changed files with 1 additions and 1 deletions
|
|
@ -100,7 +100,7 @@ func (e *ExtraRecordsMan) Run() {
|
||||||
|
|
||||||
e.updateRecords()
|
e.updateRecords()
|
||||||
|
|
||||||
// If a file is removed or renamed, fsnotify will loose track of it
|
// If a file is removed or renamed, fsnotify will lose track of it
|
||||||
// and not watch it. We will therefore attempt to re-add it with a backoff.
|
// and not watch it. We will therefore attempt to re-add it with a backoff.
|
||||||
case fsnotify.Remove, fsnotify.Rename:
|
case fsnotify.Remove, fsnotify.Rename:
|
||||||
_, err := backoff.Retry(context.Background(), func() (struct{}, error) {
|
_, err := backoff.Retry(context.Background(), func() (struct{}, error) {
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue