Incorrect Composition Resulting in `llnl-hatchet>=2025.1.0`

[michaelmckinsey1]

Temporary Fix

Use llnl-hatchet==2024.1.3 (<2025.1.0) and latest Thicket.

Problem

There is an issue that manifests when unifying profiles in Thicket, that stems from an unknown issue in hatchet, which I discovered from changing my hatchet version to an older version, which fixed the issue.

This issue can be reproduced in llnl-thicket==2025.1.0 and llnl-hatchet==2025.1.0. For example, Unifying these two calltrees in Thicket

Result in this calltree:

but with llnl-hatchet==2024.1.3, you will get

which is the expected result. My current suspicion is that the issue stems from one of the PRs that changed hatchet/readers/caliper_native_reader.py since the last release (2024.1.3)

[michaelmckinsey1]

65536-2.cali.txt
65536-2-0.cali.txt

Files to reproduce this issue (they are .txt because github blocks .cali)