Skip to content

Conversation

@taooceros
Copy link
Member

@taooceros taooceros commented Dec 8, 2020

Easy fix but compromised. I think it would be better if we can use full async instead of GetAwaitor().GetResult.
Link to #195 Explorer plugin cause threadpool task shortage.

#233 may allow this to become better if we don't need to create a new CancellationTokenSource but use the one in the main thread, and if we can make plugin use Task as result type, this can become even better that don't need to wait the result.

@taooceros taooceros requested a review from jjw24 December 8, 2020 03:29
@taooceros taooceros added the bug Something isn't working label Dec 8, 2020
@jjw24
Copy link
Member

jjw24 commented Dec 15, 2020

hey @taooceros whats the issue this is fixing? and how do i repro it?

@jjw24
Copy link
Member

jjw24 commented Dec 15, 2020

hey @taooceros whats the issue this is fixing? and how do i repro it?

all good i saw the comment in the othe PR:

image

@jjw24
Copy link
Member

jjw24 commented Dec 15, 2020

is this problem happening in dev?

@taooceros
Copy link
Member Author

is this problem happening in dev?

Not sure, but I believe it could happen.

@taooceros taooceros mentioned this pull request Jan 2, 2021
@jjw24
Copy link
Member

jjw24 commented Jan 17, 2021

is this still needed now the async model is in?

@taooceros
Copy link
Member Author

is this still needed now the async model is in?

No, I will close this one.

@taooceros taooceros closed this Jan 17, 2021
@taooceros taooceros deleted the ExplorerAsync branch January 17, 2021 09:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants