dependabot[bot] on pip
Bump traitlets from 5.2.0 to 5.… (compare)
agronholm on exceptiongroup
Expose NonBaseMultiError in tri… (compare)
agronholm on exceptiongroup
Changed open_tcp_listeners() an… (compare)
agronholm on exceptiongroup
Documentation updates (compare)
agronholm on exceptiongroup
Bump click from 8.1.2 to 8.1.3 … Bump wrapt from 1.14.0 to 1.14.… Bump traitlets from 5.1.1 to 5.… and 6 more (compare)
pquentin on pip
pquentin on master
Bump cryptography from 37.0.1 t… Merge pull request #2313 from p… (compare)
dependabot[bot] on pip
Bump ipython from 7.31.1 to 7.3… (compare)
test_checkpoints
test is constantly failing on windows/py310
If someone (another thread) does a fork between
parent, child = subprocess.socketpair()
try:
p = multiprocessing.get_context("spawn").Process(target=functools.partial(target, child=child)
p.start()
finally:
child.close()
That forked process takes a copy of the child fd and that's just "you used a thread with a fork and that's the deadlock we warned you about"?
trio
over in dask/distributed#6201 which people here may be interested in