fix: handle cache-memory cold start in issue duplication detector#3215
Conversation
The workflow reported missing_data (cache_memory_miss) on first run because issues.json doesn't exist yet. The agent gave up instead of falling through to GitHub search to populate the cache. Fix the prompt to: - Treat empty/missing cache as a normal cold start (not an error) - Explicitly instruct NOT to report missing_data on cache miss - Always search via GitHub API regardless of cache state - Use bash for file I/O instead of relying on MCP server abstractions - Document cache merge behavior for subsequent runs Fixes #3213 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR updates the Issue Duplication Detector agent prompt to handle cache-memory cold starts without reporting missing_data, and to rely on GitHub search to populate and validate duplicate candidates.
Changes:
- Clarifies that missing or empty
/tmp/gh-aw/cache-memory/issues.jsonis a normal cold start. - Reworks duplicate detection flow to compare cached data and always search GitHub.
- Adds explicit bash-based read/write instructions and cache merge guidance.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/issue-duplication-detector.md |
Updates the agent workflow prompt for cache loading, cold-start handling, GitHub search, and cache writing behavior. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 1
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
This comment has been minimized.
This comment has been minimized.
🧪 Smoke Test: Copilot BYOK (Offline) Mode
Running in BYOK offline mode ( Overall: PARTIAL PASS (GitHub MCP unavailable due to sandbox auth limitations; all other tests passed)
|
Smoke Test Results❌ GitHub API: Bad credentials (HTTP 401) Overall: FAIL (2 of 3 tests passed) The gh CLI authentication issue prevented GitHub API verification.
|
🔬 Smoke Test Results
Overall: FAIL — workflow template variables (
|
|
Smoke test: FAIL Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "registry.npmjs.org"See Network Configuration for more information.
|
🏗️ Build Test Suite Results
Overall: 8/8 ecosystems passed — ✅ PASS
|
|
Smoke test results: 2 pass, 2 fail. Overall: FAIL. Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "localhost"See Network Configuration for more information.
|
Smoke Test Results — FAIL
Overall: FAIL — Service containers unreachable from this environment.
|
|
@copilot address review feedback |
Addressed in |
Problem
The Issue Duplication Detector workflow reports
missing_data(cache_memory_miss) on its first run (or after cache expiry) because/tmp/gh-aw/cache-memory/issues.jsondoesn't exist yet. The agent treats the empty cache as an error and gives up instead of falling through to GitHub search.Root cause from run 25920514188:
The cache directory was restored (with only
cache-hit-history.json), but theissues.jsonfile has never been written because the agent always bails on the first cold start.Fix
Updated the workflow prompt to:
missing_dataon cache misscat,cat >) instead of ambiguous MCP server referencesChanges
.github/workflows/issue-duplication-detector.md— prompt rewrite for steps 1-5Fixes #3213