Hey @RobCo and @vincebowdren
While the error may look scary – the analysis (and the step) succeeds and produces the expected analysis results. We plan to fix this soon (days to weeks, not hours). Is this causing any other issues beyond an annoying log in the build summary?