You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
unexpected error causes a11y scan action to fail #22
After a lot of trial and error after getting multiple instances of the a11y scanner failing against a long list of URLs, I discovered that if this page (though copied into a different repo) is included in the list of URLs to scan, it causes the action to fail with the following message:
/home/runner/work/_temp/583e4e7e-ec11-43e3-9b15-3d2b6b0f2c17.sh: line 2: syntax error near unexpected token `('
Error: Process completed with exit code 2.
When this happens, the action will create github issues for all the detections that were found in the scan (for all files prior to the action failing), but since the action errors out, copilot never kicks off to start working on the issues that are opened. If someone tries re-running the action, duplicate issues will be logged even though they were already logged in the previous failed scan(s).
Hopefully this is enough information to look into this so a fix can be made.
A fix for this has now shipped in v1 (v1.6.0) and in v2 (v2.2.0), so I’m closing this issue. Thanks again for reporting it, and please let us know if you run into additional issues (or if this one still repros for you)!
Activity
smockle commentedon Oct 21, 2025
Thanks for reporting this @scottaohara! I appreciate you including a page (https://scottaohara.github.io/testing/failing-cookie-region.html) where this repros; that made this much easier to debug. I opened #36 with a fix. I’ll keep this issue open until that fix is backported to the v1 and v2 series.
fix(Find): Replace single quotes in Finding’s `html` field (#36)
chore: Backport #36 to the `v1` branch (#39)
chore: Backport #36 to the `v2` branch (#38)
smockle commentedon Oct 22, 2025
A fix for this has now shipped in v1 (v1.6.0) and in v2 (v2.2.0), so I’m closing this issue. Thanks again for reporting it, and please let us know if you run into additional issues (or if this one still repros for you)!