-
Notifications
You must be signed in to change notification settings - Fork 246
Start indexing and resolving Rubydex graph #3992
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
Open
vinistock
wants to merge
1
commit into
rubydex_adoption_feature_branch
Choose a base branch
from
03-03-start_indexing_and_resolving_rubydex_graph
base: rubydex_adoption_feature_branch
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+24
−4
Open
Changes from all commits
Commits
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
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
Oops, something went wrong.
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.
Should this be inside its own
Thread.newblock as well, like the existing indexing? Or is Rubydex handling it in some other wayThere 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.
The old indexing happens inside a thread because it's too slow and we don't want to block requests while we're still indexing.
Rubydex is fast enough that we don't have to run indexing in a thread, which will simplify a lot of our code.
For example, right now, we need code to bust the code lens cache and trigger a refresh after indexing because we may have computed incorrect lenses if a request comes in before indexing is finished.
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.
Right now it still takes 30s to index core using rubydex, and even if we cut it down to 20s I'd argue that it's still a noticeable wait.
I'd vote for keeping it in a thread for now, so to users the behaviour is simply "background indexing got faster", instead of actually seeing longer blocking on requests?
And after fully migrated to rubydex, we see how fast we can realistically get to and what cleanups will be worth the tradeoff.
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.
The asynchronous aspect of indexing is the source of various bugs, so I would prefer we invert the decision here. Remove the complexity and revisit if users actually complain it's too slow.
For example, #3639 is difficult to fix properly with async indexing. We have the code lens hack to prevent issues, but we also have a terrible hack in file watched events to keep sleeping and re-enqueuing until indexing is complete.
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.
I see. If it clears out many bugs at once then let's do it then.
Do you have a fully list of such bugs/cleanups somewhere so we don't forget to do them or parellalize the work?