Repository navigation
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
|
@pgoldberg Thank you for this fix. Are you OK with signing the CLA? |
|
Hey @acozzette, just signed it, thanks! |
|
@pgoldberg I'm not able to see your repro, I wonder if it needs to be made publicly visible? |
|
@acozzette Sorry about that — I just made it public! |
|
Can we get that scenario as a test case within this PR? If something is broken it needs a test case to ensure it doesn't break again... Note we need to be vary cautious touching this stuff and I'll have to take a deeper look next week once you have a test in this PR... |
|
Hey @jbedard, thanks for taking a look! I added a new e2e test that mirrors the setup in my minimal repro, as well as a more direct test that The e2e test and |
Since #2559, packages with lifecycle hooks only get direct dependencies in
deps, butnpm_package_storeassumes that any package whose store target doesn't havesrc(which still are both packages with lifecycle hooks and packages with circular deps) have their entire transitive closure indeps. It only setstransitive_filesto the direct dependencies'filesfor those packages, which means that now, packages with lifecycle hooks have incompletetransitive_files.Changes are visible to end-users: yes
NpmPackageStoreInfo.transitive_filesnow includes the transitive deps of npm packages that have lifecycle hooks.Test plan
minimal repro here: https://github.com/pgoldberg/rules_js_lifecycle_transitive_repro