-
Notifications
You must be signed in to change notification settings - Fork 136
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
mining-proxy needs graceful death instead of panic #484
Comments
Please tag as "good first issue"! |
@bcral i’d like to work on this. |
@Priceless-P Yes, that's correct. |
I haven't and probably won't get to it soon. |
Just a heads-up @Priceless-P - to implement this the |
Okay. Thank you for letting me know. @darricksee |
@bcral i would like to work on this issue, can you assign it to me. |
Hi @SumantxD, I am currently working on it. |
@Priceless-P ok fine |
Hey is anyone working on this issue ? If not please assign this to me . |
Hey @mihir1739 it seems @Priceless-P is working on it here #518 |
@Priceless-P what is the status on this? why was #518 closed without being merged? |
@plebhash Yes. |
Is this up for grabs? @Priceless-P |
The mining-proxy seems to be panicking on closure. This makes test coverage data impossible to retrieve with llvm-cov.
This same issue used to exist on the pool and TProxy until it was fixed by #432
The text was updated successfully, but these errors were encountered: