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

Proposal: Fixes #286 - EventLoopScheduler - unexpected Exception after Dispose #288

Closed
wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Oct 31, 2016

  • Added unique id as objectName when creating ObjectDisposedException
  • EventLoopScheduler.Run() -> catch & handle ObjectDisposedException

…n after Dispose

- Added unique id as objectName when creating ObjectDisposedException
- EventLoopScheduler.Run() -> catch & handle ObjectDisposedException
@dnfclas
Copy link

dnfclas commented Oct 31, 2016

Hi @DanielMue, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

@dnfclas
Copy link

dnfclas commented Oct 31, 2016

@DanielMue, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.

Thanks, DNFBOT;

@akarnokd
Copy link
Collaborator

Is this still a problem?

@HebuSan
Copy link

HebuSan commented Jun 6, 2018

Yes, It Is !

#286

A fix would be great, or, if not validated, explanations to understand expected behaviour (there is also a stack thread on this).

@akarnokd
Copy link
Collaborator

Closing as superseeded by a simpler #969.

@akarnokd akarnokd closed this Nov 14, 2019
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.

None yet

5 participants