GitHub · Where software is built

Backwards-incompatible changes - SUBSCRIBE TO THIS THREAD if you use trio!
#1 · njsmith opened on Jan 22, 2017
13
Tracking issue: intermittent test failures
#200 · njsmith opened on Jun 11, 2017
49

Labels Milestones New issue

Give a better error for improper combinations of AsyncExitStack with nurseries

#1243

· vxgmichel opened

on Oct 8, 2019

Stack spew when quitting via the debugger

#1155

· smurfix opened

on Jul 25, 2019

Make the TrioInternalError experience less confusing

#1056

· njsmith opened

on May 17, 2019

Provide a helper to dump the task tree / stack tree

#927

· njsmith opened

on Feb 13, 2019

Busy-waiting watchdog

#672

· belm0 opened

on Sep 17, 2018

Add a blocked task watchdog

design discussion

#591

· njsmith opened

on Aug 4, 2018

Provide an equivalent of curio.monitor

#413

· Nikratio opened

on Jan 20, 2018

Update introspection API for recent changes in nurseries

design discussion

potential API breaker

#386

· njsmith opened

on Dec 22, 2017

Tools for finding scheduler-dependent "heisenbugs"

design discussion

pytest-trio relevant

#239

· njsmith opened

on Jul 2, 2017

Can we make forgetting an await be an error?

#79

· njsmith opened

on Mar 10, 2017

It'd be nice if we had a test helper for systematically injecting cancellations

design discussion

pytest-trio relevant

#77

· njsmith opened

on Mar 10, 2017

How can we help catch the mistake of issuing a blocking operation without a timeout set?

design discussion

#62

· njsmith opened

on Feb 26, 2017