ConfigWatcher is triggering multiple events for a single modification of a file
Closed this issue · 4 comments
adietish commented
See redhat-developer/intellij-kubernetes#640 for more details on this. It seems to be a know defect on Linux/Windows.
adietish commented
@datho7561 found out that the sequence of events come in 3 cases:
@datho7561:
here are three cases:
- 1st event: the file is empty, 2nd event: then complete
- 1st event: the file is incomplete, 2nd event: then complete
- 1st event: the file is complete, 2nd event: then complete (again)
adietish commented
We therefore think that we need to prevent events from be propagated where the kube config file does not exist, is empty or is not valid yaml (incomplete file)
adietish commented
@datho7561: @olkornii is back ready to test things. I'll therefore make sure we have a fix that he can test.