# Pitfall Log / 踩坑日志

项目：kedro-org/kedro

摘要：发现 31 个潜在踩坑项，其中 5 个为 high/blocking；最高优先级：安装坑 - 来源证据：Add exclude_pipelines parameter to find_pipelines。

## 1. 安装坑 · 来源证据：Add exclude_pipelines parameter to find_pipelines

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

## 2. 安装坑 · 来源证据：Kedro x MLRun

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Kedro x MLRun
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/kedro-org/kedro/issues/5305 | 来源类型 github_issue 暴露的待验证使用条件。

## 3. 安装坑 · 来源证据：ci: Nightly build failure on `develop`

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：ci: Nightly build failure on `develop`
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/kedro-org/kedro/issues/5601 | 来源类型 github_issue 暴露的待验证使用条件。

## 4. 安装坑 · 来源证据：ci: Nightly build failure on `main`

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：ci: Nightly build failure on `main`
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/kedro-org/kedro/issues/5600 | 来源类型 github_issue 暴露的待验证使用条件。

## 5. 维护坑 · 来源证据：Revise and update AWS deployment docs

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个维护/版本相关的待验证问题：Revise and update AWS deployment docs
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/kedro-org/kedro/issues/5304 | 来源类型 github_issue 暴露的待验证使用条件。

## 6. 安装坑 · 失败模式：installation: 1.0.0

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

## 7. 安装坑 · 失败模式：installation: 1.1.0

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

## 8. 安装坑 · 失败模式：installation: 1.2.0

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

## 9. 安装坑 · 失败模式：installation: 1.3.0

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

## 10. 安装坑 · 失败模式：installation: 1.4.0

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

## 11. 安装坑 · 来源证据：Document how to add docs with MkDocs when the docs tool is not selected

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Document how to add docs with MkDocs when the docs tool is not selected
- 对用户的影响：可能影响升级、迁移或版本选择。
- 证据：community_evidence:github | https://github.com/kedro-org/kedro/issues/5603 | 来源类型 github_issue 暴露的待验证使用条件。

## 12. 安装坑 · 来源证据：Fix the `docs` tool so generated Sphinx docs build correctly

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Fix the `docs` tool so generated Sphinx docs build correctly
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/kedro-org/kedro/issues/5592 | 来源类型 github_issue 暴露的待验证使用条件。

## 13. 安装坑 · 来源证据：Packages settings are not used when running a package pipeline from project root dir

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Packages settings are not used when running a package pipeline from project root dir
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/kedro-org/kedro/issues/5515 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 14. 安装坑 · 来源证据：kedro new accepts project names that shadow Python stdlib modules / keywords, silently producing a broken project

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：kedro new accepts project names that shadow Python stdlib modules / keywords, silently producing a broken project
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/kedro-org/kedro/issues/5607 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 15. 配置坑 · 失败模式：configuration: Packages settings are not used when running a package pipeline from project root dir

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Packages settings are not used when running a package pipeline from project root dir
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Packages settings are not used when running a package pipeline from project root dir
- 证据：failure_mode_cluster:github_issue | https://github.com/kedro-org/kedro/issues/5515 | Packages settings are not used when running a package pipeline from project root dir

## 16. 配置坑 · 失败模式：configuration: Review & update Kedro deployment docs for AWS Step Functions

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Review & update Kedro deployment docs for AWS Step Functions
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Review & update Kedro deployment docs for AWS Step Functions
- 证据：failure_mode_cluster:github_issue | https://github.com/kedro-org/kedro/issues/5364 | Review & update Kedro deployment docs for AWS Step Functions

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

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

## 18. 维护坑 · 失败模式：migration: 0.19.15

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

## 19. 维护坑 · 失败模式：migration: 1.0.0rc3

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

## 20. 维护坑 · 失败模式：migration: Document how to add docs with MkDocs when the docs tool is not selected

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: Document how to add docs with MkDocs when the docs tool is not selected
- 对用户的影响：Developers may hit a documented source-backed failure mode: Document how to add docs with MkDocs when the docs tool is not selected
- 证据：failure_mode_cluster:github_issue | https://github.com/kedro-org/kedro/issues/5603 | Document how to add docs with MkDocs when the docs tool is not selected

## 21. 维护坑 · 失败模式：migration: Fix the `docs` tool so generated Sphinx docs build correctly

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: Fix the `docs` tool so generated Sphinx docs build correctly
- 对用户的影响：Developers may hit a documented source-backed failure mode: Fix the `docs` tool so generated Sphinx docs build correctly
- 证据：failure_mode_cluster:github_issue | https://github.com/kedro-org/kedro/issues/5592 | Fix the `docs` tool so generated Sphinx docs build correctly

## 22. 维护坑 · 失败模式：migration: kedro new accepts project names that shadow Python stdlib modules / keywords, silently produc...

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: kedro new accepts project names that shadow Python stdlib modules / keywords, silently producing a broken project
- 对用户的影响：Developers may hit a documented source-backed failure mode: kedro new accepts project names that shadow Python stdlib modules / keywords, silently producing a broken project
- 证据：failure_mode_cluster:github_issue | https://github.com/kedro-org/kedro/issues/5607 | kedro new accepts project names that shadow Python stdlib modules / keywords, silently producing a broken project

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

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

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

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

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

## 26. 能力坑 · 失败模式：capability: Add exclude_pipelines parameter to find_pipelines

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Add exclude_pipelines parameter to find_pipelines
- 对用户的影响：Developers may hit a documented source-backed failure mode: Add exclude_pipelines parameter to find_pipelines
- 证据：failure_mode_cluster:github_issue | https://github.com/kedro-org/kedro/issues/5582 | Add exclude_pipelines parameter to find_pipelines

## 27. 能力坑 · 失败模式：capability: Kedro x MLRun

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Kedro x MLRun
- 对用户的影响：Developers may hit a documented source-backed failure mode: Kedro x MLRun
- 证据：failure_mode_cluster:github_issue | https://github.com/kedro-org/kedro/issues/5305 | Kedro x MLRun

## 28. 能力坑 · 失败模式：capability: ci: Nightly build failure on `develop`

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: ci: Nightly build failure on `develop`
- 对用户的影响：Developers may hit a documented source-backed failure mode: ci: Nightly build failure on `develop`
- 证据：failure_mode_cluster:github_issue | https://github.com/kedro-org/kedro/issues/5601 | ci: Nightly build failure on `develop`

## 29. 能力坑 · 失败模式：conceptual: Revise and update AWS deployment docs

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this conceptual risk before relying on the project: Revise and update AWS deployment docs
- 对用户的影响：Developers may hit a documented source-backed failure mode: Revise and update AWS deployment docs
- 证据：failure_mode_cluster:github_issue | https://github.com/kedro-org/kedro/issues/5304 | Revise and update AWS deployment docs

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

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

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

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