Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Add a "nursery_end" instrumentation. #1317
Conversation
The use case: One of your tasks raises an exception. The nursery cancels all other tasks and waits for them to end. If one of these tasks swallows the cancellation, e.g. because of a deadlock, you need a way to find the original exception.
Codecov Report
@@ Coverage Diff @@
## master #1317 +/- ##
==========================================
- Coverage 99.69% 99.67% -0.02%
==========================================
Files 106 106
Lines 13008 13042 +34
Branches 996 998 +2
==========================================
+ Hits 12968 13000 +32
- Misses 23 25 +2
Partials 17 17
|
|
I think it's unnecessary to have a separate It looks like you're also calling |
as per @oremanj's feedback
|
Fair enough, thanks for the feedback. Fixed. |
|
Umm, Azure seems not to have picked up the latest change ? |
… except that we don't have that yet. @njsmith OK to simply add an |
|
… or I could simply set |
|
Ah, for some reason I thought we already passed the final outcome to the instrument... my bad! I'm going to defer to @njsmith on the backwards compatibility policy for instruments. |
The use case: One of your tasks raises an exception. The nursery cancels
all other tasks and waits for them to end. If one of these tasks
swallows the cancellation, e.g. because of a deadlock, you need a way
to find the original exception.