-
Notifications
You must be signed in to change notification settings - Fork 30
fix(rhino-importer): Use main thread always for document creation #1161
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8 changes: 8 additions & 0 deletions
8
Importers/Rhino/Speckle.Importers.Rhino/Internal/ImporterInstanceFactory.cs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| using Microsoft.Extensions.Logging; | ||
|
|
||
| namespace Speckle.Importers.Rhino.Internal; | ||
|
|
||
| internal sealed class ImporterInstanceFactory(Sender sender, ILogger<ImporterInstance> logger) | ||
| { | ||
| public ImporterInstance Create(ImporterArgs args) => new(args, sender, logger); | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the main change. We're opening the document here on construction of the importer.
This way, we're doing it on the main thread.
Previously, this was done from a .NET worker thread inside the
Task.Runblock lower down.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why would we ever need to run things on a worker thread in an importer environment?
re your PR desc, even if McNeel fixes, is not the safe to run always on main?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. There's another issue with Rhino inside where, as soon as the main thread is yielded (via the
awaitkeyword), It will be hogged for ever by something internal to Rhino.This means, once an
awaitkeyword is used, anywhere, then we've lost control over the main thread now for the remaining process life span.This means we have to be careful to use the main thread first, and then use async after.
That's what this PR achieves. but it's working around several weird behaviours of Rhino Inside.
I get the impression that Rhino Inside wasn't really built to be very compatible with await async, since none of the examples from mcneel involve async.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sense to me, got it thanks!
I hope i am not annoying but what stop us to run everything sync?