# Pitfall Log / 踩坑日志

项目：PrefectHQ/prefect

摘要：发现 22 个潜在踩坑项，其中 0 个为 high/blocking；最高优先级：安装坑 - 失败模式：installation: 3.7.4 - From cradle to grave。

## 1. 安装坑 · 失败模式：installation: 3.7.4 - From cradle to grave

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

## 2. 安装坑 · 失败模式：installation: 3.7.4.dev3: Nightly Development Release

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

## 3. 安装坑 · 来源证据：Concurrent subflow calls adopt the WRONG subflow's persisted result on parent flow retry (positional dynamic_key race)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Concurrent subflow calls adopt the WRONG subflow's persisted result on parent flow retry (positional dynamic_key race)
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/PrefectHQ/prefect/issues/22259 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 4. 安装坑 · 来源证据：Leaked `ephemeral-*` Redis consumer groups pin the `events` stream and prevent trimming after ungraceful shutdowns

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Leaked `ephemeral-*` Redis consumer groups pin the `events` stream and prevent trimming after ungraceful shutdowns
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/PrefectHQ/prefect/issues/22136 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 5. 配置坑 · 失败模式：configuration: 3.7.4.dev4: Nightly Development Release

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

## 6. 配置坑 · 失败模式：configuration: 3.7.5 - No run left CANCELLING

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

## 7. 配置坑 · 失败模式：configuration: 3.7.5.dev1: Nightly Development Release

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

## 8. 配置坑 · 失败模式：configuration: 3.7.5.dev2: Nightly Development Release

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

## 9. 配置坑 · 失败模式：configuration: 3.7.5.dev3: Nightly Development Release

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

## 10. 配置坑 · 失败模式：configuration: 3.7.5.dev4: Nightly Development Release

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

## 11. 配置坑 · 失败模式：configuration: 3.7.5.dev5: Nightly Development Release

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

## 12. 配置坑 · 失败模式：configuration: 3.7.5.dev6: Nightly Development Release

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

## 13. 配置坑 · 失败模式：configuration: Leaked `ephemeral-*` Redis consumer groups pin the `events` stream and prevent trimming after...

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Leaked `ephemeral-*` Redis consumer groups pin the `events` stream and prevent trimming after ungraceful shutdowns
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Leaked `ephemeral-*` Redis consumer groups pin the `events` stream and prevent trimming after ungraceful shutdowns
- 证据：failure_mode_cluster:github_issue | https://github.com/PrefectHQ/prefect/issues/22136 | Leaked `ephemeral-*` Redis consumer groups pin the `events` stream and prevent trimming after ungraceful shutdowns

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

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

## 15. 运行坑 · 失败模式：runtime: Broken test harness due to missing routes attribute in PrefectRouter

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this runtime risk before relying on the project: Broken test harness due to missing routes attribute in PrefectRouter
- 对用户的影响：Developers may hit a documented source-backed failure mode: Broken test harness due to missing routes attribute in PrefectRouter
- 证据：failure_mode_cluster:github_issue | https://github.com/PrefectHQ/prefect/issues/22307 | Broken test harness due to missing routes attribute in PrefectRouter

## 16. 维护坑 · 来源证据：Broken test harness due to missing routes attribute in PrefectRouter

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个维护/版本相关的待验证问题：Broken test harness due to missing routes attribute in PrefectRouter
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/PrefectHQ/prefect/issues/22307 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

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

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

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

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

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

## 20. 能力坑 · 失败模式：capability: Concurrent subflow calls adopt the WRONG subflow's persisted result on parent flow retry (pos...

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Concurrent subflow calls adopt the WRONG subflow's persisted result on parent flow retry (positional dynamic_key race)
- 对用户的影响：Developers may hit a documented source-backed failure mode: Concurrent subflow calls adopt the WRONG subflow's persisted result on parent flow retry (positional dynamic_key race)
- 证据：failure_mode_cluster:github_issue | https://github.com/PrefectHQ/prefect/issues/22259 | Concurrent subflow calls adopt the WRONG subflow's persisted result on parent flow retry (positional dynamic_key race)

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

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

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

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