-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
RuntimeError when switching projects with watchdog>=2.0.0 #14803
Comments
Spyder 5.0.3 with watchdog 2.1.1: I no longer see the watchdog RuntimeError when switching projects. However I see a Qt error. Could be openSUSE specific though, as we don't pin to PyQt5 < 5.13:
|
I can confirm that the original post is NOT resolved with ERROR:fsevents:Unhandled exception in FSEventsEmitter
Traceback (most recent call last):
File "/Users/rclary/opt/miniconda3/envs/spy-dev/lib/python3.9/site-packages/watchdog/observers/fsevents.py", line 309, in run
_fsevents.add_watch(self, self.watch, self.events_callback, self.pathnames)
RuntimeError: Cannot add watch <ObservedWatch: path=/Users/rclary/Documents/Python/c2w, is_recursive=True> - it is already scheduled
Dependencies
|
I wonder if this issue is related to #14787... |
One more note: Even with watchdog 1.0.2, I get the above error about |
Okay, I can confirm that the OP still manifests when running from bootstrap in a pyenv environment with Pyenv environment: RuntimeError
|
@bnavigator , it actually looks like your first error is editor_id = self.editor_ids[self.current_editor]
KeyError: <spyder.plugins.outlineexplorer.editor.OutlineExplorerProxyEditor object at 0x7f0efd7ea280> which means that |
Okay, I can also confirm that the OP still manifests when running from bootstrap in a pyenv environment with watchdog=2.1.2 and PyQt5=5.15.4, and I cannot reproduce @bnavigator's Pyenv environment: RuntimeError
As further clarification, regardless of launch environment, the OP issue only results in the error posting to the launch terminal, NOT the internal Python interpreter and does NOT produce an Issue Reporter pop-up window. This means that running a standalone macOS app does NOT make this issue visible to the user. The issue still occurs, however, as it is reported to the Terminal when launching in this manner
|
could this Watchdog constraint be only limited to MacOS ? so non-MacOS Users would be not impacted ? |
Can anyone test this on Windows or Ubuntu? I've pushed up branch constrain-watchdog if that's helpful. |
Reviewing my first comment in this issue, I now remember that this is no longer an issue on |
Problem Description
The advent of
watchdog>2.0.0
manifested several issues, one of which was solved withwatchdog=2.0.2
but uncovered aRuntimeError
. See #14779.watchdog>1.0.2
is not yet available on conda main channel, so bootstrap requires updating via conda-forge in order to manifest the issue.What steps reproduce the problem?
Paste Traceback/Error Below (if applicable)
Versions
Dependencies
Dependencies
The text was updated successfully, but these errors were encountered: