[Common] DPL Analysis: fix malformed index declaration #13960
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aalkin
requested review from
a team,
alibuild,
ddobrigk,
iarsene,
jgrosseo and
ktf
as code owners
|
O2 linter results: ❌ 0 errors, |
github-actions
bot
changed the title
yakparo
pushed a commit
to yakparo/O2Physics
that referenced
this pull request
Nov 29, 2025
…13960) Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
lmattei01
pushed a commit
to lmattei01/O2Physics
that referenced
this pull request
Dec 5, 2025
…13960) Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The proper index table declaration requires all of the columns to be pointing to the tables that, themselves, point to the Key table. Reworked index-builder in O2 will be enforcing this requirement, thus the compilation of the current declaration will fail. Since the automatic
Builds<>mechanism is not used for this table (it would not work due to the fact that the first column, BC index, refers to the table -BCs- that does not have an index to the Key -Occs) and the table is filled normally throughProduces<>, this change is fully transparent and will not affect anything analysis-wise.@ktf @ddobrigk