Today I noticed the first freeze report for a plugin in the new „Freezes“ tab on the Marketplace.
However, there is no note of the plugin version, which caused the freeze.
With obfuscated code, it‘s difficult or not possible to find the cause because the stacktrace is not helpful enough.
Could the version of the plugin be added to the freeze reports, please?
As an aside, if you’re having trouble with the obfuscated trace (I’m presuming ZKM), are you:
Capturing the ZKM changelog as part of every release build (and ideally committing it back to the repository)?
If yes on 1, are you performing incremental obfuscation (by providing the previous changelog as an obfuscation input), so obfuscated names are stable across releases?
I do both of these and generally have no issue with decoding obfuscated traces (though I hand it all to an agent rather than dealing with ZKM’s UI for this).
Hi, this is unfortunately expected as we do not always perfectly match guilty plugin in IDE, we are improving that in 2026.3 and you will be able to see version more often
@dseptimus I keep the logs, of course, and de-obfuscation is not a problem (using Signoz MCP with an agent now and point it at the logs). But without a version it‘s not overly useful, even if I used incremental obfuscation (lines change, etc).