# Pitfall Log / 踩坑日志

项目：apify/crawlee

摘要：发现 22 个潜在踩坑项，其中 1 个为 high/blocking；最高优先级：维护坑 - 来源证据：Add support for Bun runtime - Issue with `browser-pool` and `memory-storage` packages。

## 1. 维护坑 · 来源证据：Add support for Bun runtime - Issue with `browser-pool` and `memory-storage` packages

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个维护/版本相关的待验证问题：Add support for Bun runtime - Issue with `browser-pool` and `memory-storage` packages
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/apify/crawlee/issues/2046 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 2. 配置坑 · 失败模式：configuration: v3.15.1

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

## 3. 配置坑 · 失败模式：configuration: v3.16.0

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

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

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

## 5. 运行坑 · 失败模式：runtime: v3.15.0

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

## 6. 运行坑 · 失败模式：runtime: v3.15.3

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

## 7. 运行坑 · 失败模式：runtime: v3.17.0

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

## 8. 运行坑 · 来源证据：Crawler hangs forever when given malformed request input (e.g. invalid `userData` shape)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：Crawler hangs forever when given malformed request input (e.g. invalid `userData` shape)
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/apify/crawlee/issues/3764 | 来源类型 github_issue 暴露的待验证使用条件。

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

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

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

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

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

## 12. 能力坑 · 失败模式：capability: Allow disabling ImpitHttpClient client cache

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Allow disabling ImpitHttpClient client cache
- 对用户的影响：Developers may hit a documented source-backed failure mode: Allow disabling ImpitHttpClient client cache
- 证据：failure_mode_cluster:github_issue | https://github.com/apify/crawlee/issues/3769 | Allow disabling ImpitHttpClient client cache

## 13. 能力坑 · 失败模式：capability: Crawler hangs forever when given malformed request input (e.g. invalid `userData` shape)

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Crawler hangs forever when given malformed request input (e.g. invalid `userData` shape)
- 对用户的影响：Developers may hit a documented source-backed failure mode: Crawler hangs forever when given malformed request input (e.g. invalid `userData` shape)
- 证据：failure_mode_cluster:github_issue | https://github.com/apify/crawlee/issues/3764 | Crawler hangs forever when given malformed request input (e.g. invalid `userData` shape)

## 14. 运行坑 · 失败模式：performance: Add support for Bun runtime - Issue with `browser-pool` and `memory-storage` packages

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: Add support for Bun runtime - Issue with `browser-pool` and `memory-storage` packages
- 对用户的影响：Developers may hit a documented source-backed failure mode: Add support for Bun runtime - Issue with `browser-pool` and `memory-storage` packages
- 证据：failure_mode_cluster:github_issue | https://github.com/apify/crawlee/issues/2046 | Add support for Bun runtime - Issue with `browser-pool` and `memory-storage` packages

## 15. 运行坑 · 失败模式：performance: Merge @crawlee/memory-storage package into @crawlee/core

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: Merge @crawlee/memory-storage package into @crawlee/core
- 对用户的影响：Developers may hit a documented source-backed failure mode: Merge @crawlee/memory-storage package into @crawlee/core
- 证据：failure_mode_cluster:github_issue | https://github.com/apify/crawlee/issues/3756 | Merge @crawlee/memory-storage package into @crawlee/core

## 16. 运行坑 · 失败模式：performance: v3.15.2

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

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

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

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

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

## 19. 维护坑 · 失败模式：maintenance: v3.13.10

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

## 20. 维护坑 · 失败模式：maintenance: v3.13.9

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

## 21. 维护坑 · 失败模式：maintenance: v3.14.0

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

## 22. 维护坑 · 失败模式：maintenance: v3.14.1

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