Is anyone familiar with this error: ```ValueError:...
# general
Is anyone familiar with this error:
Copy code
ValueError: Failed to begin watching the filesystem: Bad file descriptor (os error 9)
👀 1
I don't think I've seen that. What Pants version? Is it deterministic?
yes, and 2.2.0
it keeps happening on one of my coworker's machines
Copy code
13:05:26.06 [ERROR] Failed to begin watching the filesystem: Bad file descriptor (os error 9)
Traceback (most recent call last):
  File "/home/larry/.cache/pants/setup/bootstrap-Linux-x86_64/2.2.0_py38/lib/python3.8/site-packages/pants/bin/", line 157, in single_daemonized_run
    scheduler = self._core.prepare_scheduler(options_bootstrapper)
  File "/home/larry/.cache/pants/setup/bootstrap-Linux-x86_64/2.2.0_py38/lib/python3.8/site-packages/pants/pantsd/", line 112, in prepare_scheduler
    self._init_scheduler(options_fingerprint, options_bootstrapper)
  File "/home/larry/.cache/pants/setup/bootstrap-Linux-x86_64/2.2.0_py38/lib/python3.8/site-packages/pants/pantsd/", line 90, in _init_scheduler
    raise e
  File "/home/larry/.cache/pants/setup/bootstrap-Linux-x86_64/2.2.0_py38/lib/python3.8/site-packages/pants/pantsd/", line 79, in _init_scheduler
    self._scheduler = EngineInitializer.setup_graph(
  File "/home/larry/.cache/pants/setup/bootstrap-Linux-x86_64/2.2.0_py38/lib/python3.8/site-packages/pants/init/", line 177, in setup_graph
    return EngineInitializer.setup_graph_extended(
  File "/home/larry/.cache/pants/setup/bootstrap-Linux-x86_64/2.2.0_py38/lib/python3.8/site-packages/pants/init/", line 282, in setup_graph_extended
    scheduler = Scheduler(
  File "/home/larry/.cache/pants/setup/bootstrap-Linux-x86_64/2.2.0_py38/lib/python3.8/site-packages/pants/engine/internals/", line 156, in __init__
    self._scheduler = native.new_scheduler(
  File "/home/larry/.cache/pants/setup/bootstrap-Linux-x86_64/2.2.0_py38/lib/python3.8/site-packages/pants/engine/internals/", line 291, in new_scheduler
full stack trace
killing the
process didn't help, clearing out
didn't help
What happens if you run with
same issue
hm, do you have a stacktrace with
? I'd expect it to be different than above Note that
is different than killing Pantsd process -
means you won't start a new daemon process
well I would provide that, except a reboot of the computer in question appears to have cleared up the error
👀 1
working theory is some sort of file lock
Hmm this is unfortunate. Please report back if it happens again!