Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
RuntimeError when switching projects with watchdog>=2.0.0
See original GitHub issueProblem Description
The advent of watchdog>2.0.0 manifested several issues, one of which was solved with watchdog=2.0.2 but uncovered a RuntimeError. 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?
- Switch from one project to another
- Switch back to original project
- Spyder issue reporter launches
Paste Traceback/Error Below (if applicable)
File "watchdog/observers/fsevents.pyc", line 283, in run
RuntimeError: Cannot add watch <ObservedWatch: path=/Users/rclary/Documents/Python/spyder-kernels, is_recursive=True> - it is already scheduled
Versions
- Spyder version: 4.2.2 None
- Python version: 3.9.1 64-bit
- Qt version: 5.12.10
- PyQt5 version: 5.12.3
- Operating System: Darwin 19.6.0
Dependencies
Dependencies
# Mandatory:
applaunchservices >=0.1.7 : 0.2.1 (OK)
atomicwrites >=1.2.0 : 1.4.0 (OK)
chardet >=2.0.0 : 4.0.0 (OK)
cloudpickle >=0.5.0 : 1.6.0 (OK)
diff_match_patch >=20181111 : 20200713 (OK)
intervaltree >=3.0.2 : 3.1.0 (OK)
IPython >=7.6.0 : 7.20.0 (OK)
jedi =0.17.2 : 0.17.2 (OK)
jsonschema >=3.2.0 : 3.2.0 (OK)
keyring >=17.0.0 : 22.0.1 (OK)
nbconvert >=4.0 : 6.0.7 (OK)
numpydoc >=0.6.0 : 1.1.0 (OK)
parso =0.7.0 : 0.7.0 (OK)
pexpect >=4.4.0 : 4.8.0 (OK)
pickleshare >=0.4 : 0.7.5 (OK)
psutil >=5.3 : 5.8.0 (OK)
pygments >=2.0 : 2.8.0 (OK)
pylint >=1.0 : 2.7.0 (OK)
pyls >=0.36.2;<1.0.0 : 0.36.2 (OK)
pyls_black >=0.4.6 : 0.4.6 (OK)
pyls_spyder >=0.3.2 : 0.3.2 (OK)
qdarkstyle >=2.8 : 2.8.1 (OK)
qtawesome >=0.5.7 : 1.0.2 (OK)
qtconsole >=5.0.1 : 5.0.2 (OK)
qtpy >=1.5.0 : 1.9.0 (OK)
setuptools >=39.0.0 : 52.0.0 (OK)
sphinx >=0.6.6 : 3.5.1 (OK)
spyder_kernels >=1.10.2;<1.11.0 : 1.10.2 (OK)
textdistance >=4.2.0 : 4.2.1 (OK)
three_merge >=0.1.1 : 0.1.1 (OK)
watchdog >=0.10.3 : 2.0.2 (OK)
zmq >=17 : 22.0.3 (OK)
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
(re)start and watchdog timing is fragile; leads to device not ...
RuntimeError : Failed to find device after booting, error message: ... Thursday I'll change the connect timeout in depthai-core and see if ...
Read more >The URScript Programming Language for e- Series
information herein is subject to change without notice and should not be construed as a ... 16.1.1. enable_external_ft_sensor(enable, sensor_mass=0.0, ...
Read more >MACHINELOGIC
MachineLogic projects and MachineLogic Runtime: Describes resources, tasks, and pre-emptive scheduling. • Downloading, controlling, and debugging: Provides ...
Read more >DC FunRef.book - Cika
When a runtime error occurs, the following information is passed to the error ... change anything in any of the parameters while doing...
Read more >Rexroth IndraMotion MTX Diagnosis Messages - Bosch Rexroth
Before switching on the device, the equipment grounding conductor must have been permanently connected to all electrical equipment in accord-.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
could this Watchdog constraint be only limited to MacOS ? so non-MacOS Users would be not impacted ?
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
KeyError.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