[agentics] Failed runs
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
This is an automatically managed parent issue, not a specific change request; start by opening a linked sub-issue and following its workflow run URL. Use gh aw logs <workflow-run-url> or gh aw audit <run-id> to inspect the failure; this parent issue is done only as an organizational tracker and should not be closed manually.
由索引模型根据 Issue 内容生成。
描述
This issue tracks all failures from agentic workflows in this repository. Each failed workflow run creates a sub-issue linked here for organization and easy filtering.
Purpose
This parent issue helps you:
- View all workflow failures in one place by checking the sub-issues below
- Filter out failure issues from your main issue list using
no:parent-issue - Track the health of your agentic workflows over time
Sub-Issues
All individual workflow failure issues are linked as sub-issues below. Click on any sub-issue to see details about a specific failure.
Troubleshooting Failed Workflows
Using agentic-workflows Agent (Recommended)
Agent: agentic-workflows
Purpose: Debug and fix workflow failures
Instructions:
- Invoke the agent: Type
/agentin GitHub Copilot Chat and select agentic-workflows - Provide context: Tell the agent to debug the workflow failure
- Supply the workflow run URL for analysis
- The agent will:
- Analyze failure logs
- Identify root causes
- Propose specific fixes
- Validate solutions
Using gh aw CLI
You can also debug failures using the gh aw CLI:
# Download and analyze workflow logs
gh aw logs <workflow-run-url>
# Audit a specific workflow run
gh aw audit <run-id>
Manual Investigation
- Click on a sub-issue to see the failed workflow details
- Follow the workflow run link in the issue
- Review the agent job logs for error messages
- Check the workflow configuration in your repository
Resources
This issue is automatically managed by GitHub Agentic Workflows. Do not close this issue manually.
- expires on Feb 23, 2026, 1:49 PM UTC
- 主要语言
- C#
- 星标
- 1.8k
- 派生
- 268
- 平均合并
- 2 小时 35 分钟
- 30 天内合并 PR
- 136
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
npgsql/efcore.pg 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
NTS: the M ordinate is dropped from geometry SQL literals and from geometries stored in JSON可能已有人在做 @Ahmed7991 于 5 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 85/100
npgsql/efcore.pg#4093 · 1 条评论 ·
维护者通常 1 天内回复
-
`TimeSpan`/`Duration` component members: negative values are floored, and intervals computed in SQL are read field by field可能已有人在做 @jeremy-morren 于 11 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
Numeric storage parameters are formatted with the current culture, so migrations emit 0,01 instead of 0.01可能已有人在做 @Sorbitol 于 12 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 30/100
维护者通常 1 天内回复
-
`Contains` on a JSON primitive collection compares JSON text, so `DateTime` and `TimeOnly` items never match可能已有人在做 @Mr444-dev 于 7 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 45/100
npgsql/efcore.pg#4099 · 1 条评论 ·
维护者通常 1 天内回复
相似的 Issue
-
Issue-Bug Needs-Triage
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
JiaFeiMiao-K-Cat/DiscImageStudio#281 ·
维护者通常 1 天内回复
-
area/access-management Frontend onboarding candidate :handshake:
难度 2/5 1-3 小时 新手友好度 65/100
Altinn/altinn-auth#4941 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
aws/aws-sdk-net#4586 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
Kryptos-FR/MarkView.Avalonia#269 · 1 个 reaction ·
维护者通常 1 天内回复