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.

Loop that handles pid is closed

See original GitHub issue

Trying to use playwrigth through asyncio.

OS: macOS Catalina version 10.15.7 Python version: 3.9.1

My code run pretty well doing all tasks but at the and i keep getting:

Loop <_UnixSelectorEventLoop running=False closed=True debug=True> that handles pid 1675 is closed

full debug log:

DEBUG:asyncio:<_UnixReadPipeTransport fd=12 idle> pauses reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 polling> resumes reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 idle> pauses reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 polling> resumes reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 idle> pauses reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 polling> resumes reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 idle> pauses reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 polling> resumes reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 idle> pauses reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 polling> resumes reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 idle> pauses reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 polling> resumes reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 idle> pauses reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 polling> resumes reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 idle> pauses reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 polling> resumes reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 idle> pauses reading
DEBUG:asyncio:<_UnixReadPipeTransport fd=12 polling> resumes reading
DEBUG:aioredis:Closed 1 connection(s)
DEBUG:asyncio:Close <_UnixSelectorEventLoop running=False closed=False debug=True>
DEBUG:asyncio:process 1675 exited with returncode 0
WARNING:asyncio:Loop <_UnixSelectorEventLoop running=False closed=True debug=True> that handles pid 1675 is closed

Can someone explain why?

Issue Analytics

State:
Created 3 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

oiwncommented, Mar 3, 2021

Yes, i can. Will post update.

0reactions

pavelfeldmancommented, Mar 30, 2021

Keeping our bug database clean, so closing everything non-actionable. Please file a new request with the snippet when you have a chance!

Top Results From Across the Web

Python3 Flask asyncio subprocess in route hangs

The vast majority of Flask deployments will use threads to handle incoming requests. ... %r that handles pid %r is closed", loop, pid)...

Issue 41320: async process closing after event loop closed

Loop <_UnixSelectorEventLoop running=False closed=True debug=False> that handles pid 1257652 is closed case 2.

Introduction to Closed-Loop Control and PID - Barr Group

Systems that utilize feedback are called closed-loop control systems. The feedback is used to make decisions about changes to the control signal ...

How to Optimize Closed-Loop Control Through a Better ...

To reduce the process variable error, the closed-loop control function in PID controllers is commonly used. A PID controller reads a process variable...

Understanding PID Loop Process Control - Vertech

PID control is one of the most commonly used closed-loop control ... To summarize, a PID Loop controls a process based on three...