Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add instrumentation hooks #20

Open
smurfix opened this issue Apr 30, 2018 · 1 comment
Open

Add instrumentation hooks #20

smurfix opened this issue Apr 30, 2018 · 1 comment

Comments

@smurfix
Copy link
Collaborator

smurfix commented Apr 30, 2018

Trio-asyncio runs in a separate Trio task. The current instrumentation hooks for Trio capture when that task is running (or not), but not what it's doing internally. Thus I probably need to think about adding a couple of new hooks that report queuing/removing timers/callbacks.

@oremanj
Copy link
Member

oremanj commented May 9, 2020

From #37, moved here to consolidate: "Use trio's instrumentation to add some callbacks related to trio_asyncio. Specifically, queuing and executing asyncio handles should be more tractable."

I think instead of adding our own hooks we might want to create one asyncio task per Trio task and vice versa and use coroutine transportation as discussed in #42.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants