Open
Conversation
There seems to be a race condition when a file is loaded where some properties are set and then later read as nil. This attempts to fix this by saving non-nil properties to the global state and reading from that. Seems to eliminate the problem so far.
Author
|
Eh, I don't think this is a full fix just yet. The issues with |
|
i have similar problem maybe related to this issue |
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
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.
There seems to be a race condition (see #19) when a file is loaded where some
properties are set and then later read as nil. This attempts to fix
this by saving non-nil properties to the global state and reading from
that. Seems to eliminate the problem so far.