task: fix panic when dropping LocalSet
#1843
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
It turns out that the
Scheduler::release
method onLocalSet
'sScheduler
is called, when theScheduler
is dropped with tasksstill running. Currently, that method is
unreachable!
, which meansthat dropping a
LocalSet
with tasks running will panic.Solution
This commit fixes the panic, by pushing released tasks to
pending_drop
. This is the same asBasicScheduler
.I've also added a test that reproduces the panic. The test fails
against master.
Fixes #1842
Signed-off-by: Eliza Weisman eliza@buoyant.io