# Pitfall Log / 踩坑日志

项目：topoteretes/cognee

摘要：发现 32 个潜在踩坑项，其中 10 个为 high/blocking；最高优先级：安装坑 - 来源证据：Enhancement: Add retrieval quality benchmarks for different search modes。

## 1. 安装坑 · 来源证据：Enhancement: Add retrieval quality benchmarks for different search modes

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Enhancement: Add retrieval quality benchmarks for different search modes
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/topoteretes/cognee/issues/2913 | 来源类型 github_issue 暴露的待验证使用条件。

## 2. 安装坑 · 来源证据：[Bug]: JSON issue while adding the file for Cognify the data

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：[Bug]: JSON issue while adding the file for Cognify the data
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/topoteretes/cognee/issues/3079 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 3. 配置坑 · 来源证据：[Bug]: Duplicate content generated in BeautifulSoupLoader due to overlapping default extraction rules

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：[Bug]: Duplicate content generated in BeautifulSoupLoader due to overlapping default extraction rules
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/topoteretes/cognee/issues/3154 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 4. 安全/权限坑 · 失败模式：security_permissions: cognee.add silently creates a new owner-scoped dataset when non-owner uses an existing datase...

- 严重度：high
- 证据强度：source_linked
- 发现：Developers should check this security_permissions risk before relying on the project: cognee.add silently creates a new owner-scoped dataset when non-owner uses an existing dataset name
- 对用户的影响：Developers may expose sensitive permissions or credentials: cognee.add silently creates a new owner-scoped dataset when non-owner uses an existing dataset name
- 证据：failure_mode_cluster:github_issue | https://github.com/topoteretes/cognee/issues/2846 | cognee.add silently creates a new owner-scoped dataset when non-owner uses an existing dataset name

## 5. 安全/权限坑 · 失败模式：security_permissions: cognee.search ignores ACL when resolving dataset by name for non-owners

- 严重度：high
- 证据强度：source_linked
- 发现：Developers should check this security_permissions risk before relying on the project: cognee.search ignores ACL when resolving dataset by name for non-owners
- 对用户的影响：Developers may expose sensitive permissions or credentials: cognee.search ignores ACL when resolving dataset by name for non-owners
- 证据：failure_mode_cluster:github_issue | https://github.com/topoteretes/cognee/issues/2845 | cognee.search ignores ACL when resolving dataset by name for non-owners

## 6. 安全/权限坑 · 失败模式：security_permissions: cognify pipeline silently skips data added by non-owner users

- 严重度：high
- 证据强度：source_linked
- 发现：Developers should check this security_permissions risk before relying on the project: cognify pipeline silently skips data added by non-owner users
- 对用户的影响：Developers may expose sensitive permissions or credentials: cognify pipeline silently skips data added by non-owner users
- 证据：failure_mode_cluster:github_issue | https://github.com/topoteretes/cognee/issues/2847 | cognify pipeline silently skips data added by non-owner users

## 7. 安全/权限坑 · 来源证据：[Feature]: Temporal freshness policies for stale and superseded memories

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：[Feature]: Temporal freshness policies for stale and superseded memories
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/topoteretes/cognee/issues/3004 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 8. 安全/权限坑 · 来源证据：cognee.add silently creates a new owner-scoped dataset when non-owner uses an existing dataset name

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：cognee.add silently creates a new owner-scoped dataset when non-owner uses an existing dataset name
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/topoteretes/cognee/issues/2846 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 9. 安全/权限坑 · 来源证据：cognee.search ignores ACL when resolving dataset by name for non-owners

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：cognee.search ignores ACL when resolving dataset by name for non-owners
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/topoteretes/cognee/issues/2845 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 10. 安全/权限坑 · 来源证据：cognify pipeline silently skips data added by non-owner users

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：cognify pipeline silently skips data added by non-owner users
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/topoteretes/cognee/issues/2847 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 11. 安装坑 · 失败模式：installation: v1.0.8

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v1.0.8
- 对用户的影响：Upgrade or migration may change expected behavior: v1.0.8
- 证据：failure_mode_cluster:github_release | https://github.com/topoteretes/cognee/releases/tag/v1.0.8 | v1.0.8

## 12. 安装坑 · 失败模式：installation: v1.0.9

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v1.0.9
- 对用户的影响：Upgrade or migration may change expected behavior: v1.0.9
- 证据：failure_mode_cluster:github_release | https://github.com/topoteretes/cognee/releases/tag/v1.0.9 | v1.0.9

## 13. 安装坑 · 失败模式：installation: v1.1.0.dev1

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v1.1.0.dev1
- 对用户的影响：Upgrade or migration may change expected behavior: v1.1.0.dev1
- 证据：failure_mode_cluster:github_release | https://github.com/topoteretes/cognee/releases/tag/v1.1.0.dev1 | v1.1.0.dev1

## 14. 安装坑 · 来源证据：Relax the exact `ladybug==0.16.0` pin — blocks downstream updates (0.16.1 / 0.17.1 available)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Relax the exact `ladybug==0.16.0` pin — blocks downstream updates (0.16.1 / 0.17.1 available)
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/topoteretes/cognee/issues/2976 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 15. 配置坑 · 失败模式：configuration: LiteLLM ignores custom LLM_ENDPOINT for OpenAI-compatible APIs

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: LiteLLM ignores custom LLM_ENDPOINT for OpenAI-compatible APIs
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: LiteLLM ignores custom LLM_ENDPOINT for OpenAI-compatible APIs
- 证据：failure_mode_cluster:github_issue | https://github.com/topoteretes/cognee/issues/2842 | LiteLLM ignores custom LLM_ENDPOINT for OpenAI-compatible APIs

## 16. 配置坑 · 失败模式：configuration: [Bug]: JSON issue while adding the file for Cognify the data

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: [Bug]: JSON issue while adding the file for Cognify the data
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: [Bug]: JSON issue while adding the file for Cognify the data
- 证据：failure_mode_cluster:github_issue | https://github.com/topoteretes/cognee/issues/3079 | [Bug]: JSON issue while adding the file for Cognify the data

## 17. 配置坑 · 失败模式：configuration: [Feature]: Temporal freshness policies for stale and superseded memories

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: [Feature]: Temporal freshness policies for stale and superseded memories
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: [Feature]: Temporal freshness policies for stale and superseded memories
- 证据：failure_mode_cluster:github_issue | https://github.com/topoteretes/cognee/issues/3004 | [Feature]: Temporal freshness policies for stale and superseded memories

## 18. 配置坑 · 失败模式：configuration: v1.1.0

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: v1.1.0
- 对用户的影响：Upgrade or migration may change expected behavior: v1.1.0
- 证据：failure_mode_cluster:github_release | https://github.com/topoteretes/cognee/releases/tag/v1.1.0 | v1.1.0

## 19. 配置坑 · 失败模式：configuration: v1.1.1

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: v1.1.1
- 对用户的影响：Upgrade or migration may change expected behavior: v1.1.1
- 证据：failure_mode_cluster:github_release | https://github.com/topoteretes/cognee/releases/tag/v1.1.1 | v1.1.1

## 20. 配置坑 · 失败模式：configuration: v1.1.1.dev0

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: v1.1.1.dev0
- 对用户的影响：Upgrade or migration may change expected behavior: v1.1.1.dev0
- 证据：failure_mode_cluster:github_release | https://github.com/topoteretes/cognee/releases/tag/v1.1.1.dev0 | v1.1.1.dev0

## 21. 配置坑 · 来源证据：[Bug]: PostgresAdapter.get_neighborhood fails on PostgreSQL 16 — unnest(:seeds) needs text[] cast

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：[Bug]: PostgresAdapter.get_neighborhood fails on PostgreSQL 16 — unnest(:seeds) needs text[] cast
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/topoteretes/cognee/issues/2933 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 22. 能力坑 · 能力判断依赖假设

- 严重度：medium
- 证据强度：source_linked
- 发现：README/documentation is current enough for a first validation pass.
- 对用户的影响：假设不成立时，用户拿不到承诺的能力。
- 证据：capability.assumptions | https://github.com/topoteretes/cognee | README/documentation is current enough for a first validation pass.

## 23. 运行坑 · 失败模式：runtime: PR Review: feat/staging-bridge-fix — Fix None reactions crash

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this runtime risk before relying on the project: PR Review: feat/staging-bridge-fix — Fix None reactions crash
- 对用户的影响：Developers may hit a documented source-backed failure mode: PR Review: feat/staging-bridge-fix — Fix None reactions crash
- 证据：failure_mode_cluster:github_issue | https://github.com/topoteretes/cognee/issues/3065 | PR Review: feat/staging-bridge-fix — Fix None reactions crash

## 24. 运行坑 · 来源证据：PR Review: feat/staging-bridge-fix — Fix None reactions crash

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：PR Review: feat/staging-bridge-fix — Fix None reactions crash
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/topoteretes/cognee/issues/3065 | 来源类型 github_issue 暴露的待验证使用条件。

## 25. 维护坑 · 失败模式：migration: v1.0.7

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: v1.0.7
- 对用户的影响：Upgrade or migration may change expected behavior: v1.0.7
- 证据：failure_mode_cluster:github_release | https://github.com/topoteretes/cognee/releases/tag/v1.0.7 | v1.0.7

## 26. 维护坑 · 失败模式：migration: v1.1.0.dev0

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: v1.1.0.dev0
- 对用户的影响：Upgrade or migration may change expected behavior: v1.1.0.dev0
- 证据：failure_mode_cluster:github_release | https://github.com/topoteretes/cognee/releases/tag/v1.1.0.dev0 | v1.1.0.dev0

## 27. 维护坑 · 失败模式：migration: v1.1.2

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: v1.1.2
- 对用户的影响：Upgrade or migration may change expected behavior: v1.1.2
- 证据：failure_mode_cluster:github_release | https://github.com/topoteretes/cognee/releases/tag/v1.1.2 | v1.1.2

## 28. 维护坑 · 维护活跃度未知

- 严重度：medium
- 证据强度：source_linked
- 发现：未记录 last_activity_observed。
- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。
- 证据：evidence.maintainer_signals | https://github.com/topoteretes/cognee | last_activity_observed missing

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 证据：downstream_validation.risk_items | https://github.com/topoteretes/cognee | no_demo; severity=medium

## 30. 安全/权限坑 · 存在评分风险

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 对用户的影响：风险会影响是否适合普通用户安装。
- 证据：risks.scoring_risks | https://github.com/topoteretes/cognee | no_demo; severity=medium

## 31. 维护坑 · issue/PR 响应质量未知

- 严重度：low
- 证据强度：source_linked
- 发现：issue_or_pr_quality=unknown。
- 对用户的影响：用户无法判断遇到问题后是否有人维护。
- 证据：evidence.maintainer_signals | https://github.com/topoteretes/cognee | issue_or_pr_quality=unknown

## 32. 维护坑 · 发布节奏不明确

- 严重度：low
- 证据强度：source_linked
- 发现：release_recency=unknown。
- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。
- 证据：evidence.maintainer_signals | https://github.com/topoteretes/cognee | release_recency=unknown