Fix error when calling coroutine with await in _ready #44104
Merged
Conversation
This file contains 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
|
Already fixed as part of #43890, closing. |
The code paths for calling async functions seemed to be missing in some cases, causing a debug break and false positive error.
|
Reopening as per #44101 (comment). |
pouleyKetchoupp
force-pushed
the
coroutine-await-fix
branch
from
699a7f5
to
2e4ee06
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The code paths for calling async functions seemed to be missing in some cases, causing a debug break and false positive error.
I don't know if this is the proper fix, I might be missing something. But it does fix issues I had with using await in _ready function and doesn't seem to break anything.
Fixes #44101