-
-
Couldn't load subscription status.
- Fork 1.5k
fix: add local imported packages to the packages to analyze when using cache #4424
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
Conversation
849f21e to
ccf27b4
Compare
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.
Did you do any tests (manual or otherwise) on a somewhat larger codebase and/or with a lot of local imports? Are we talking millisecond increases or can this become a cardinality bomb and grow much bigger than that?
The fix looks good and is understandable so I'll approve this since I have full trust in your judgement here 😄
Did you do any tests (manual or otherwise) on a somewhat larger codebase and/or with a lot of local imports?
I didn't do a benchmark because this depends on how many direct packages a package depends on, so it's difficult to create accurate benchmarks.
Are we talking millisecond increases or can this become a cardinality bomb and grow much bigger than that?
As it just adds the direct packages related to one analyzed package and not the indirect packages, the cardinality is limited.
But if a package depends on thousands of local packages (I hope nobody does that), the impact will be important on performances (only for the run after the first one) but I don't have a better solution.
EDIT: I have some doubts maybe the real problem is the linter 🤔
@gabolaev
gabolaev
left a comment
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.
It works, thank you!
ccf27b4 to
98c486b
Compare
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.
LGTM
Uh oh!
There was an error while loading. Please reload this page.
To reproduce the problem:
If it works you should see:
but if it not works:
This will impact negatively the performance of a run with a cache but it will increase the stability of reports.
Fixes #4423