Similar to https://github.com/xrootd/xrootd/issues/1198 I've found that XRootD's Python bindings break Python's subprocess module. Unlike on Linux it's trivially reproducible:
```python
$ python -c 'import XRootD.client; eos = XRootD.client.FileSystem("root://eoslhcb.cern.ch/"); eos.dirlist("/eos"); import subprocess; subprocess.check_output(["ls"])' (logse-sqlite)
KQ: bad file descriptor polling for events
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/Users/cburr/mambaforge/envs/logse-sqlite/lib/python3.10/subprocess.py", line 420, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/Users/cburr/mambaforge/envs/logse-sqlite/lib/python3.10/subprocess.py", line 524, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['ls']' died with <Signals.SIGABRT: 6>.
```
I guess the other three `XrdSysIOEventsPoll` implementations need to have a similar patch applied to only abort if the parent PID doesn't match.
--
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/1673
You are receiving this because you are subscribed to this thread.
Message ID: <[log in to unmask]>
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
