mirror of
https://github.com/milvus-io/milvus.git
synced 2026-07-21 02:05:41 +00:00
d4b1957f03
## Summary Add a new issue template (`agentic_bug_report.md`) optimized for AI Agent to analyze, reproduce, and fix Milvus bugs autonomously. ### Why The existing `bug_report.yaml` is designed for human users with free-text fields. For an AI agent workflow (auto-analyze → locate code → write fix → submit PR), we need more structured, machine-actionable information. ### Template Structure | Section | Purpose | |---------|---------| | **Environment** | Version (image tag / commit), deployment mode, SDK — for agent to checkout matching code and set up environment | | **Reproduction Script** | Self-contained, runnable Python/Go script ending with assertion — agent can execute directly | | **Reproduction Steps** | Alternative for systemic/stability/timing issues that can't be scripted | | **Trigger Conditions** | Frequency, timing, boundary conditions — helps agent narrow down code paths | | **Expected / Actual Behavior** | Structured comparison — defines "fixed" criteria for agent verification | | **Error Logs** | Key stack traces with file:line — agent can jump directly to suspect code | | **Non-default Configuration** | Config diff only — agent knows defaults, only needs deltas | | **Analysis Hints** | Optional clues: suspect code location, related PRs, ruled-out directions | ### Design Principles - Every field directly serves a step in the agent's workflow: understand → reproduce → locate → fix → verify - Reproduction script is preferred (functional bugs) but structured steps are accepted (stability/timing bugs) - Minimal required fields to reduce filing friction while maximizing agent effectiveness 🤖 Generated with [Claude Code](https://claude.ai/code) Signed-off-by: yanliang567 <yanliang.qiao@zilliz.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>