并行压力和高次数循环若指向共享或生产系统,可能造成额外负载
原文依据:3 处处理偶发问题时,Skill 指示将触发器循环 100 次、并行运行并增加压力,但没有把这些动作限定在本地或隔离环境,也没有规定并发或请求上限。
若复现目标是共享、付费或生产服务,测试可能消耗配额、抬高费用、影响其他用户,或触发速率限制和防护告警。
对偶发故障的活动指令明确要求循环触发 100 次、并行执行并增加压力,却没有在该指令中限定只能针对本地或隔离系统,也没有并发、请求或费用上限。如果复现命令误指向共享、付费或生产服务,可能增加负载、费用、告警或数据副作用。用户可要求作者把压力复现默认限制在本地测试环境,并在任何远程目标上运行前确认目标、速率和预算。
The goal is not a clean repro but a **higher reproduction rate**. Loop the trigger 100×, parallelise, add stress, narrow timing windows, inject sleeps. A 50%-flake bug is debuggable; 1% is not, so keep raising the rate until it's debuggable.查看另外 2 个位置
### Non-deterministic bugsThe goal is not a clean repro but a **higher reproduction rate**. Loop the trigger 100×, parallelise, add stress, narrow timing windows, inject sleeps. A 50%-flake bug is debuggable; 1% is not, so keep raising the rate until it's debuggable.1. **Failing test** at whatever seam reaches the bug: unit, integration, e2e.2. **Curl / HTTP script** against a running dev server.3. **CLI invocation** with a fixture input, diffing stdout against a known-good snapshot.4. **Headless browser script** (Playwright / Puppeteer) that drives the UI and asserts on DOM/console/network.5. **Replay a captured trace.** Save a real network request / payload / event log to disk; replay it through the code path in isolation.