Improve handling of missing/invalid inputs in TrackingAssocValueMapsProducer#50730
Conversation
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-50730/49017 |
|
A new Pull Request was created by @Parsifal-2045 for master. It involves the following packages:
@battibass, @cmsbuild, @ftorrresd can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
type ngt |
|
enable nano |
|
please test |
|
+1 Size: This PR adds an extra 24KB to repository Comparison SummarySummary:
Nano size comparison Summary:
NANO Comparison SummarySummary:
|
|
+1 |
|
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. @sextonkennedy, @ftenchini, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
|
just for the record, once #50748 gets merged, we should be able to test this module from the |
|
+1 |
PR description:
This PR fixes the incorrect handling of missing/invalid inputs in
TrackingAssocValueMapsProducer.@elenavernazza (thank you!) found out that when running the
NanoPixelTablessequence without the Validation step, the job would crash withThis happens because the
associatorrequired byTrackingAssocValueMapsProduceris only produced on the fly in the validation sequence. However, the module should simply return emptyvalueMapsin these cases, which it now correctly does.PR validation:
Before this PR, running
would fail, while the workflow now runs and produces the expected "empty"
valueMaps(filled with default values).