Skip to content

MSDO Issue Triage Assistant #85

MSDO Issue Triage Assistant

MSDO Issue Triage Assistant #85

Triggered via issue April 2, 2026 09:40
@AraHaanAraHaan
commented on #189 49b663b
Status Failure
Total duration 5m 46s
Artifacts 4

msdo-issue-assistant.lock.yml

on: issue_comment
Fit to window
Zoom out
Zoom in

Annotations

9 errors, 2 warnings, and 1 notice
agent
Oops! Something went wrong! :(\\n2026-02-25T08:13:25.7899905Z ##[error]ESLint: 9.29.0\\n2026-02-25T08:13:25.7901294Z ##[error]No files matching the pattern \\u0026#34;**/*.{js,ts}\\u0026#34; were found. - \\n2026-02-25T08:13:25.7901998Z ##[error]Please check for typing mistakes in the pattern.\\n\\nThis is on the same commit hash as previously ran.\\n\\nThe only differences we can see in the logs are:\\n\\n- The tools have started downloading from https://msdous.pkgs.visualstudio.com when previously it always downloaded from https://msdoeu.pkgs.visualstudio.com. There has been no configuration change in the Azure Managed DevOps Pool configuration, the agents are deployed to \\u0026#34;West Europe\\u0026#34;.\\n- The order the tools are run has changed. Previously the Tool Applicability Information, Install and exection all showed the order as:\\n - templateanalyzer, eslint, checkov, iacfilescanner\\n The order now is:\\n - iacfilescanner, eslint, checkov, templateanalyzer\\n\\nI have validated the contents of the .json files the task downloads from the EU/US and can see no differences except that the EU server only lists the 1.0.16+ versions of the Tools.Configuration.\",\"state\":\"open\",\"html_url\":\"https://github.com/microsoft/security-devops-action/issues/189\",\"user\":{\"login\":\"a-teece\",\"id\":33296869,\"profile_url\":\"https://github.com/a-teece\",\"avatar_url\":\"https://avatars.githubusercontent.com/u/33296869?v=4\"},\"author_association\":\"NONE\",\"labels\":[\"needs-maintainer\"],\"assignees\":[\"DimaBir\"],\"comments\":13,\"reactions\":{\"total_count\":0,\"+1\":0,\"-1\":0,\"laugh\":0,\"confused\":0,\"heart\":0,\"hooray\":0,\"rocket\":0,\"eyes\":0},\"created_at\":\"2026-02-25T12:36:27Z\",\"updated_at\":\"2026-04-02T09:40:24Z\"}","type":"text"}]}}}
agent
Oops! Something went wrong! :(\\n2026-02-25T08:13:25.7899905Z ##[error]ESLint: 9.29.0\\n2026-02-25T08:13:25.7901294Z ##[error]No files matching the pattern \\u0026#34;**/*.{js,ts}\\u0026#34; ...`
agent
Oops! Something went wrong! :(\\n2026-02-25T08:13:25.7899905Z ##[error]ESLint: 9.29.0\\n202...`
agent
Oops! Something went wrong! :(\\n2026-02-25T08:13:25.7899905Z ##[error]ESLint: 9.29.0\\n2026-02-25T08:13:25.7901294Z ##[error]No files matching the pattern \\u0026#34;**/*.{js,ts}\\u0026#34; were found. -...`
safe_outputs
2 safe output(s) failed: - add_labels: Resource not accessible by personal access token - add_comment: Resource not accessible by personal access token
safe_outputs
✗ Message 2 (add_comment) failed: Resource not accessible by personal access token
safe_outputs
Failed to add comment: Resource not accessible by personal access token
safe_outputs
✗ Message 1 (add_labels) failed: Resource not accessible by personal access token
safe_outputs
Failed to add labels: Resource not accessible by personal access token
agent
GitHub MCP guard policy automatically applied for public repository. min-integrity='approved' and repos='all' ensure only approved-integrity content is accessible.
safe_outputs
2 message(s) failed to process
agent
Safe Outputs MCP Server Startup Log

Artifacts

Produced during runtime
Name Size Digest
activation Expired
4.1 KB
sha256:d0cf2bc638ececc0d0da593743ca8465ec4d13ac70955a535e04b802d972fd7d
agent
134 KB
sha256:2ec204244403ddb62283b6f8649095b3ae520b245cafec3b0db327e9276683ef
detection
2.29 KB
sha256:e33bc31ae1eb38d48da7cfd854be84cb968e91d8a59fb17fbad98b1672aa7a7e
safe-output-items
162 Bytes
sha256:c41efbacac5ea71593b75cc2f1856c7333af2a7a7b53cb347751167f7059b1f2