Skip to content

Recompute lib_path on every fine-grained incremental run #4981

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 1 commit into from
Apr 27, 2018
Merged

Conversation

msullivan
Copy link
Collaborator

This fixes some crashes and false positives when creating or removing
init.py files that do not appear in the build.

This just factors out the existing implementation of lib_path
computation and reuses it. It is somewhat inefficient and should be
improved on if we are going to call it on every fine-grained update.

I would like to cherry-pick this into 0.600 (#4946).
There is going to be a follow up PR immediately that optimizes the lib_path recomputation, but the case for cherry-picking that is a lot harder to make than for just a straightforward bug fix.
The cost of recomputing every time is about ~125ms on S.

This fixes some crashes and false positives when creating or removing
__init__.py files that do not appear in the build.

This just factors out the existing implementation of lib_path
computation and reuses it. It is somewhat inefficient and should be
improved on if we are going to call it on every fine-grained update.
Copy link
Collaborator

@JukkaL JukkaL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for fixing this!

@JukkaL JukkaL merged commit e13315d into master Apr 27, 2018
msullivan added a commit that referenced this pull request Apr 27, 2018
This fixes some crashes and false positives when creating or removing
__init__.py files that do not appear in the build.

This just factors out the existing implementation of lib_path
computation and reuses it. It is somewhat inefficient and should be
improved on if we are going to call it on every fine-grained update.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants