[kubernetes/kubernetes] fsnotify/fsnotify - Healthy or not? (Issue #138812)

DRANK

dims created an issue (kubernetes/kubernetes#138812) Please see slack starting here: https://kubernetes.slack.com/archives/CHGFYJVAN/p1778072569822999 TL;DR We need to watch this very carefully and if necessary evaluate the forks or consider forking it ourselves. Notes from @thaJeztah ``` thaJeztah  [9:02 AM] (moving from a DM I sent to [@dims](https://kubernetes.slack.com/team/U0Y7A2MME)) :warning: This is scary stuff (I recall we once discussed maintenance status of the repository); mattn is a well-known maintainer/contributor in the ecosystem, and it’s a widely used dependency (translation in thread); https://x.com/mattn_jp/status/2051929334995427791?s=46&t=Y92XZlAhVJRKCtPDml0Csg thaJeztah  [9:06 AM] :point_up: also having a discussion internally on our Docker slack; at least to keep a close eye (latest release was done by mattn and looks to be some bug-fixes) Looks like he started a fork; so we need to look which repository to use going forward; at least keep an eye on updates. Not sure if anyone here has a personal contact with either mattn or other maintainer(s) of the project  https://x.com/mattn_jp/status/2051952716369568164?s=46&t=MkU30GvdnwzIRLI1J_frDg https://github.com/gofsnotify/fsnotify ``` follow up comment from @soltysh: ``` soltysh  [9:11 AM] for others that looked at repos, it's too close to miss https://github.com/fsnotify/fsnotify/ is the old one, vs the new being https://github.com/gofsnotify/fsnotify [9:12 AM]notice fsnotify vs go fsnotify in the org name (edited) ``` -- Reply to this email directly or view it on GitHub: https://github.com/kubernetes/kubernetes/issues/138812 You are receiving this because you are subscribed to this thread. Message ID: <kubernetes/kubernetes/issues/138812@github.com>