-
Notifications
You must be signed in to change notification settings - Fork 323
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
Could not recursively list files error #7695
Comments
As far as I can see |
We can try to update the library first https://mvnrepository.com/artifact/io.methvin/directory-watcher |
The change upgrades `directory-watcher` library, hoping that it will fix the problem reported in #7695 (there has been a number of bug fixes in MacOS listener since then). Once upgraded, tests in `WatcherAdapterSpec` because the logic that attempted to ensure the proper initialization order in the test using semaphore was wrong. Now starting the watcher using `watchAsync` which only returns the future when the watcher successfully registers for paths. Ideally authors of the library would make the registration bit public (https://github.com/gmethvin/directory-watcher/blob/3218d68a845ebd803ebd98af3be4692d1b63e12c/core/src/main/java/io/methvin/watcher/DirectoryWatcher.java#L229C7-L229C20) but it is the best we can do so far. Had to adapt to the new API in PathWatcher as well, ensuring the right order of initialization.
Hubert Plociniczak reports a new STANDUP for yesterday (2023-10-31): Progress: Address remaining comments for custom log levels PR #8162. Investigating possible solutions to #7695, limited by the rather closed API of the directory-watcher library. It should be finished by 2023-11-01. Next Day: Next day I will be working on the #7695 task. Prepare a potential workaround for the bug. |
The change upgrades `directory-watcher` library, hoping that it will fix the problem reported in #7695 (there has been a number of bug fixes in MacOS listener since then). Once upgraded, tests in `WatcherAdapterSpec` because the logic that attempted to ensure the proper initialization order in the test using semaphore was wrong. Now starting the watcher using `watchAsync` which only returns the future when the watcher successfully registers for paths. Ideally authors of the library would make the registration bit public (https://github.com/gmethvin/directory-watcher/blob/3218d68a845ebd803ebd98af3be4692d1b63e12c/core/src/main/java/io/methvin/watcher/DirectoryWatcher.java#L229C7-L229C20) but it is the best we can do so far. Had to adapt to the new API in PathWatcher as well, ensuring the right order of initialization. Should fix #7695.
Hubert Plociniczak reports a new STANDUP for yesterday (2023-11-01): Progress: Prepared a PR with the upgrade and some workarounds for potential race-condition. Helped with #7935. Discussing some serialization improvements, Trying to reproduce #8174 on a recent bookclub but nothing so far. It should be finished by 2023-11-01. Next Day: Next day I will be working on the #8174 task. Continue with the investigation. |
@PabloBuchu 🤞 this should fix it but if not, please reopen if you see this again |
Wild stacktrace appeared while I was opening a local project in Enso. Creating an issue after short talk with @hubertp
The text was updated successfully, but these errors were encountered: