Skip to content

Fix potential hash collisions of traceql StringArray + compare() improvement #2404

Fix potential hash collisions of traceql StringArray + compare() improvement

Fix potential hash collisions of traceql StringArray + compare() improvement #2404

Triggered via pull request November 8, 2025 22:21
Status Success
Total duration 1m 6s
Artifacts 1

self-zizmor.yaml Required

on: pull_request
Check whether there are things to scan
7s
Check whether there are things to scan
Run zizmor from current branch (self test)  /  job-workflow-ref
15s
Run zizmor from current branch (self test) / job-workflow-ref
Run zizmor from current branch (self test)  /  Generate and upload zizmor results 🌈
33s
Run zizmor from current branch (self test) / Generate and upload zizmor results 🌈
Fit to window
Zoom out
Zoom in

Annotations

1 error
Run zizmor from current branch (self test) / job-workflow-ref
Script failed: We're unable to look up the version of the Zizmor workflow being called, so we can't fetch the `grafana` default configuration. Zizmor's own default will be used. Is the `id-token: write` permission set? If so, is this a run from a fork? Unfortunately we're unable to do this lookup for pull requests from forks currently.

Artifacts

Produced during runtime
Name Size Digest
SARIF file
394 Bytes
sha256:d4d3aee3cd45eea80f9e409fc14d25787118077daeef8c9158a913fa9751a7ab