d78d73e666
Created three documentation files to organize and prioritize 100+ open GitHub issues: - ISSUE_TRIAGE.md: Full categorization into 16 clusters by component and theme - DUPLICATES.md: Identified 6 confirmed duplicates and 7 potential duplicate clusters - PRIORITY_ROADMAP.md: Prioritized critical issues (P0-P3) with immediate action plan Key findings: - P0 issues: MCP protocol deprecation, database name config, duplicate detection - Component breakdown: core (25+), database (20+), mcp (12+), llm (12+), search (8+) - Estimated 15-25 issues can be consolidated through deduplication 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
156 lines
5.3 KiB
Markdown
156 lines
5.3 KiB
Markdown
# Duplicate GitHub Issues
|
||
|
||
**Date**: 2025-10-07
|
||
|
||
## Confirmed Duplicates (Already Marked)
|
||
|
||
### #963 - Duplicate Entities in Neo4j
|
||
- **Status**: Marked as duplicate
|
||
- **Original Issue**: #875 - Duplicate Entities in Neo4j with custom db name
|
||
- **Labels**: bug, duplicate
|
||
- **Action**: Can be closed with reference to #875
|
||
- **Notes**: Same core issue - deduplication not working properly
|
||
|
||
---
|
||
|
||
### #941 - TaskGroup Errors
|
||
- **Title**: ERROR：unhandled errors in a TaskGroup (1 sub-exception)
|
||
- **Status**: Marked as duplicate
|
||
- **Labels**: duplicate
|
||
- **Notes**: Reporter mentioned issue was previously reported in #353
|
||
- **Action**: Close with reference to original issue
|
||
|
||
---
|
||
|
||
### #920 - Timezone-Naive/Aware Datetime Comparison
|
||
- **Title**: [BUG] edge_operations.py is unable to compare a timezone-naive datetime with a timezone-aware one
|
||
- **Status**: Marked as duplicate
|
||
- **Labels**: bug, duplicate
|
||
- **Original Issue**: Likely resolved by commit 73015e9 "Fix datetime comparison errors by normalizing to UTC"
|
||
- **Action**: Close with reference to recent fix. Ask reporter to verify on latest version.
|
||
|
||
---
|
||
|
||
### #867 - MCP with GPT-oss Models
|
||
- **Title**: MPC does not work with GPT-oss:20 or 120B
|
||
- **Status**: Marked as duplicate
|
||
- **Duplicate Of**: #831 - [BUG] GPT-oss:20 and 120
|
||
- **Labels**: bug, duplicate
|
||
- **Action**: Close with reference to #831
|
||
|
||
---
|
||
|
||
### #801 - Empty Fulltext Search Results
|
||
- **Title**: [BUG] empty-result bug in episode_fulltext_search
|
||
- **Status**: Marked as duplicate
|
||
- **Labels**: bug, duplicate
|
||
- **Original Issue**: Likely #810 - Empty group_id handling issues
|
||
- **Action**: Close with reference to #810 or related search issue
|
||
|
||
---
|
||
|
||
### #787 - Rate Limit with SEMAPHORE_LIMIT
|
||
- **Title**: [BUG] Got rate limit even SEMAPHORE_LIMIT=1 in mcp server
|
||
- **Status**: Marked as duplicate
|
||
- **Labels**: bug, duplicate
|
||
- **Action**: Close with reference to original rate limiting issue
|
||
|
||
---
|
||
|
||
## Potential Duplicates (Require Investigation)
|
||
|
||
### Database Configuration Issues (Likely Related)
|
||
|
||
**#851**, **#798**, **#715** - All relate to database name handling
|
||
- **#851** - Search only connects to 'neo4j' db
|
||
- **#798** - Database name not passed through Graphiti object
|
||
- **#715** - Feature request to configure Neo4j database name
|
||
|
||
**Analysis**: These may be describing the same underlying issue. #715 appears to be the feature request, while #851 and #798 are bugs from the missing feature.
|
||
|
||
**Recommendation**: Fix the root cause and consolidate. Keep #715 as the tracking issue if implementing multi-DB support properly.
|
||
|
||
---
|
||
|
||
### Bulk Upload Failures
|
||
|
||
**#882**, **#879**, **#871**, **#658** - Bulk upload failures
|
||
- **#882** - IndexError during node resolution
|
||
- **#879** - ValidationError 'duplicates' field missing
|
||
- **#871** - Invalid JSON and index errors
|
||
- **#658** - "Bulk ingestion not possible"
|
||
|
||
**Analysis**: All appear to be bulk upload failures, potentially from same root cause in validation/schema handling.
|
||
|
||
**Recommendation**: Investigate if these are manifestations of same bug. If so, consolidate into single issue.
|
||
|
||
---
|
||
|
||
### FalkorDB Query Errors
|
||
|
||
**#815**, **#757**, **#731** - FalkorDB query errors
|
||
- **#815** - falkordb query error
|
||
- **#757** - quickstart_falkordb example query error
|
||
- **#731** - Malformed Cypher query on episode insertion
|
||
|
||
**Analysis**: May be same underlying issue with FalkorDB Cypher query generation.
|
||
|
||
**Recommendation**: Investigate if root cause is same. Could consolidate.
|
||
|
||
---
|
||
|
||
### MCP Server + Custom LLM Providers
|
||
|
||
**#565**, **#945** - OPENAI_BASE_URL issues
|
||
- **#565** - Cross-encoder ignores OPENAI_BASE_URL
|
||
- **#945** - Custom OPENAI_BASE_URL causes NaN embeddings
|
||
|
||
**Analysis**: Both relate to custom OpenAI-compatible endpoints not being respected in MCP server.
|
||
|
||
**Recommendation**: Likely same root issue - configuration not properly passed through MCP components.
|
||
|
||
---
|
||
|
||
### Ollama Compatibility
|
||
|
||
**#868**, **#831** - Ollama issues
|
||
- **#868** - Cannot get minimal example to work with Ollama
|
||
- **#831** - GPT-oss:20 and 120 (Ollama models)
|
||
|
||
**Analysis**: Both relate to Ollama model compatibility issues.
|
||
|
||
---
|
||
|
||
### Search Result Issues
|
||
|
||
**#534**, **#801**, **#810** - Search returning empty/no results
|
||
- **#534** - retrieve_episodes always returns no results
|
||
- **#801** - episode_fulltext_search empty results (marked duplicate)
|
||
- **#810** - Empty group_id handled inconsistently
|
||
|
||
**Analysis**: Likely all related to search filtering/group_id handling issues.
|
||
|
||
---
|
||
|
||
### Documentation/Setup Questions (Can Be Consolidated)
|
||
|
||
**#517**, **#530** - OpenRouter setup questions
|
||
- **#517** - How to setup with OpenRouter and Voyage
|
||
- **#530** - Does this work with Cursor AI + OpenRouter ChatGPT
|
||
|
||
**Analysis**: Same topic - using OpenRouter as provider. Could close with documentation reference.
|
||
|
||
---
|
||
|
||
## Summary
|
||
|
||
- **Confirmed Duplicates (Already Marked)**: 6 issues ready to close
|
||
- **Potential Duplicate Clusters**: 7 clusters (20+ issues) requiring investigation
|
||
- **Estimated Consolidation**: Could reduce issue count by 15-25 through deduplication
|
||
|
||
## Recommended Actions
|
||
|
||
1. **Immediate**: Close the 6 confirmed duplicates with appropriate references
|
||
2. **Investigation**: Review potential duplicate clusters to confirm root causes
|
||
3. **Consolidation**: Create tracking issues for clusters where multiple issues stem from same bug
|
||
4. **Documentation**: Several "questions" can be closed once docs are updated
|