mitmproxy
AI overview
Sign in and the AI will write an overview from our coverage.
Headlines · 2
- Testing Agent Tool Calls: Idempotency Under 504 Timeouts and Jitter
A Juejin AI article argues that quality teams testing AI agents should stop treating tool calls as simple success/failure HTTP outcomes, proposing a three-state model: confirmed success, confirmed failure, and in-doubt/timeout where the backend may have executed nothing, executed the write, or completed asynchronously. It then lays out a fault-injection proxy setup (via tools such as WireMock, Mitmproxy or a lightweight Envoy gateway) covering four cases: server executed but response timed out, client abort while the server finishes asynchronously, argument tweaks that invalidate a parameter-hash idempotency key, and repeated failures requiring exponential backoff and a circuit-breaker retry cap. The proposed assertions include exactly one database record per business key, SDK-injected X-Idempotency-Key headers that never change on retries, and explicit user-facing reporting of an undetermined business state rather than fabricating success.
掘金 · 人工智能 · 🔥 0 - 72-Hour Phone Tracking Audit Challenges the Microphone Eavesdropping Theory
第404号工位 reports a 72-hour packet-capture audit on an iPhone 15 Pro and a rooted Google Pixel 8, claiming 41.8GB of traffic and no microphone hardware wake-ups or uploaded raw audio. The article attributes apparent prediction to spatial-temporal graph modeling, private set intersection and on-device embeddings rather than background recording. These findings and the broader claims about commercial tracking practices were not independently corroborated in the supplied material.
掘金 · 人工智能 · 🔥 0
Experience and discussion from the community
Share my mitmproxy experienceAsk about mitmproxy
Nobody has shared their experience with mitmproxy yet.