Repository navigation
[aw] SqlClient Issue Auto-Triage reported incomplete result #4716
Description
Workflow Failure
Workflow: SqlClient Issue Auto-Triage
Branch: main
Run: https://github.com/dotnet/SqlClient/actions/runs/35581086795
Warning
Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.
Reasons:
-
Consumed the single add_comment quota with an accidental placeholder/test comment while debugging a tool-invocation issue (JSON stdin mode via jq/node/python were all blocked by sandbox permission errors), before posting the real triage summary for issue ArgumentException after updating Microsoft.Data.SqlClient to 7.1.0 #4715. The real triage summary was fully prepared (env now complete per author's linked repro https://github.com/andygjp/TdsParserArgumentException; recommend removing 'Auto-Triage: Waiting for Author' label) but could not be posted due to the exhausted per-run add_comment limit.
Real intended comment body (not posted): ## 🔍 Triage Summary (updated after author response) | Issue type: Bug | Environment: All required environment details provided for investigation | Area: closest fit Area\Netcore (core TdsParser decimal-parameter marshalling, no exact area label) | Duplicates: Fix | Enable transport of large decimal values with explicit Precision and Scale #4443, Cannot write decimal.MaxValue if precision/scale are set on SqlParameter #1655 | Regression: Likely regression from v7.1.0 introduced by Fix | Enable transport of large decimal values with explicit Precision and Scale #4443. Analysis: reporter writes 0M to a decimal(3,3) column and hits ArgumentException in TdsParser.TDSExecuteRPCAddParameter via AdjustDecimalScale; SqlDecimal.AdjustScale appears to compute Precision higher than declared for zero values at higher scale, a regression from Fix | Enable transport of large decimal values with explicit Precision and Scale #4443's new precision check. Author has now confirmed with a full repro repo. Next steps: assign to Copilot coding agent to investigate TdsParser.AdjustDecimalScale / TDSExecuteRPCAddParameter precision check for zero-value decimals; validate against pre-7.1.0 behavior; ensure fix does not reopen Cannot write decimal.MaxValue if precision/scale are set on SqlParameter #1655. Label 'Auto-Triage: Waiting for Author' should be removed since environment info is now complete.
This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.
Action Required
Assign this issue to an agent to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md
The failed workflow run is at https://github.com/dotnet/SqlClient/actions/runs/35581086795
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
- Start your agent
- Load the
agentic-workflowsskill from.github/skills/agentic-workflows/SKILL.mdor https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md - Type
debug the agentic workflow issue-triage failure in https://github.com/dotnet/SqlClient/actions/runs/35581086795
Tip
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:
safe-outputs:
report-failure-as-issue: falseGenerated from SqlClient Issue Auto-Triage · copilot · 65.8 AIC · ◷
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
github-actions commentedon Sep 21, 2026
Agent job 35655733263 failed.
Warning
Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.
Reasons:
add_comment limit exhausted by accidental placeholder test call
While debugging a shell permission issue with jq/python for JSON payload construction, a test call to add_comment with body 'test123' was inadvertently executed and succeeded, posting a placeholder comment to issue ArgumentException after updating Microsoft.Data.SqlClient to 7.1.0 #4715 (temporary_id aw_P5uUFQmo). This consumed the run's single add_comment quota (1 of 1), so the real on-demand /triage summary for issue ArgumentException after updating Microsoft.Data.SqlClient to 7.1.0 #4715 could not be posted. The intended real summary was prepared: Issue type=Bug, Environment=all fields now provided, Area=Area\Netcore (closest fit), Duplicates=Fix | Enable transport of large decimal values with explicit Precision and Scale #4443 and Cannot write decimal.MaxValue if precision/scale are set on SqlParameter #1655 potentially related, Regression=likely from v7.1.0 via Fix | Enable transport of large decimal values with explicit Precision and Scale #4443, with analysis of TdsParser.AdjustDecimalScale zero-value precision handling and recommendation to assign to Copilot coding agent. A maintainer should manually delete/ignore the placeholder 'test123' comment and re-run /triage, or a future run should post the prepared summary.
This is a structured incompletion signal (
report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.priyankatiwari08 commentedon Sep 22, 2026
This is a recurrence of the workflow defect tracked in #4692 and #4704, addressed by PR #4706: #4706.
The two reported September 21 runs for #4715 published
test comment bodyandtest123instead of the completed follow-up/on-demand summaries. JSON preparation commands were denied, and the agent's diagnostic comment consumed its one-comment allowance.#4706 supplies the permitted JSON preparation/submission path and adds a pre-publication validation step that rejects placeholders or incomplete summaries. It is still open;
maincontinues to run the old workflow, which explains why the problem recurred.No separate repair PR is needed for this recurrence. After #4706 is deployed, verify an updated summary on #4715 and remove only the confirmed placeholder comments after successful replacement. #4715 already has an initial summary; the missing result is the updated triage incorporating later information.
Keep this tracker open pending live verification. This automation fix does not fix or resolve the separate SqlClient regression reported in #4715.