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

do not panic on loss of oneshot channel reciever #356

Merged
merged 1 commit into from
Mar 8, 2018

Conversation

bluejekyll
Copy link
Member

fixes #355

@bluejekyll bluejekyll changed the title do not panic on loss of oneshot chanel reciever do not panic on loss of oneshot channel reciever Mar 7, 2018
@codecov
Copy link

codecov bot commented Mar 7, 2018

Codecov Report

Merging #356 into master will increase coverage by 0.01%.
The diff coverage is 75%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #356      +/-   ##
==========================================
+ Coverage   87.21%   87.23%   +0.01%     
==========================================
  Files         121      121              
  Lines       12359    12358       -1     
==========================================
+ Hits        10779    10780       +1     
+ Misses       1580     1578       -2
Impacted Files Coverage Δ
proto/src/dns_handle.rs 83.49% <75%> (+0.88%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 649217b...e08e104. Read the comment docs.

@bluejekyll bluejekyll merged commit 586544e into master Mar 8, 2018
@bluejekyll bluejekyll deleted the no_panic_complete branch March 30, 2018 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

error notifying wait, possible future leak
1 participant