Use current Namespace/Project has a bug with minikube

[olkornii]

Configurations:
Kubernetes v1.26.2 on Docker 24.0.4
openjdk 17.0.7 2023-04-18
OS: Fedora 38
Intellij 2023.1

Steps to reproduce:

1. Start minikube cluster
2. Expand Namespaces
3. Select namespace -> right click -> Use namespace -> tree refreshed (WRONG BEHAVIOR)
4. Repeat few times -> cluster name changes for short time (sometimes freezes)

On the video's 10 second is a bug.
Screencast from 2023-07-24 12-22-10.webm

[adietish]

I cannot replicate this, I'm running MacOS though which may interfere.

[adietish]

#641 prevents minikube from being displayed as <unknown context>. It does not fix the collapsing of the context though. I thus keep this issue opened.

[adietish]

It looks as if the reason for the remaining bug is that the file watcher service in the jdk would send multiple (2+) events per file for a single modification. Several reports of this exist on stackoverflow:

• https://stackoverflow.com/questions/16777869/java-7-watchservice-ignoring-multiple-occurrences-of-the-same-event
• https://stackoverflow.com/questions/72953304/prevent-java-filewatcher-to-process-the-same-file-multiple-times
• https://stackoverflow.com/questions/39147735/watchservice-fires-entry-modify-sometimes-twice-and-sometimes-once
• https://java.tutorialink.com/java-7-watchservice-ignoring-multiple-occurrences-of-the-same-event/

This only happens on Linux (and maybe Windows), not on MacOS where the file watcher service isn't native (it's polling in java).

A possible solution is to check the file timestamp and ignore subsequent notification for the same file for the same timestamp (see comment in https://java.tutorialink.com/java-7-watchservice-ignoring-multiple-occurrences-of-the-same-event/)

[adietish]

There is a filewatcher service that is native & cross-platform. It provides a native implementation for MacOS: https://github.com/gmethvin/directory-watcher/blob/main/core/src/main/java/io/methvin/watchservice/MacOSXListeningWatchService.java

[adietish]

depends on redhat-developer/intellij-common#190

[adietish]

#646 improved the situation. Minikube resource tree is still collapsing though but it is doing it less frequently. There's not much more we can do about this given that it's the jdk filesystem watch service that is causing this when notifying a single file change multiple times.

[adietish]

Closing.