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
Call callWhenNewProductsRegistered() callbacks only for branches that are present #38872
Call callWhenNewProductsRegistered() callbacks only for branches that are present #38872
Conversation
… are present This change avoids user surprises when the BranchDescription no longer has type information for dropped branches. An analysis of all current users of callWhenNewProductsRegistered() showed that all of them either explicitly limited themselves to present branches, or implicilty assumed the branch is present. I can't think of any useful use case for user code to make decisions based on dropped branches. For inspecting product history up to dropped products provenance is likely better way.
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38872/31293
|
A new Pull Request was created by @makortel (Matti Kortelainen) for master. It involves the following packages:
@cmsbuild, @smuzaffar, @Dr15Jones, @makortel can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
looks good to me |
@cmsbuild, please test |
@cmsbuild, please abort |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-155cbd/26530/summary.html Comparison SummarySummary:
|
4.53 shows the same difference as in #38603. |
@cmsbuild, please test Refresh to see if the comparison differences are gone |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-155cbd/26621/summary.html Comparison SummarySummary:
|
+1 Comparisons are now clean. |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This is a preparatory PR towards #38806. This change avoids user surprises when the BranchDescription no longer has type information for dropped branches. An analysis of all current users of callWhenNewProductsRegistered() in #38806 (comment) showed that all of them either explicitly limited themselves to present branches, or implicilty assumed the branch is present. I can't think of any useful use case for user code to make decisions based on dropped branches. For inspecting product history up to dropped products provenance is likely better way.
I made this change as a separate PR so that the change in behavior becomes clearer in release notes, and we can see any possible side effect in the IBs separately from #38806.
PR validation:
Framework unit tests pass.