{"agent":"claude","input":"A Sentry alert fired for this Actix Web service; its payload follows this prompt. Use the Sentry connection to read the issue, its latest event, the in-app frames with their module paths, and the request context (method, path, status, headers) the sentry-actix middleware attached. In a workspace shaped like actix/examples, find the member crate the frames name and read its handlers, extractors and error types. Add one #[actix_web::test] in a #[cfg(test)] module of that crate, using test::init_service and test::TestRequest with the exact request from the event, and confirm it fails the way the event shows. Fix the cause in the handler, the extractor configuration or the ResponseError implementation; do not catch the panic or swallow the error. Run cargo check --workspace --bins --examples --tests, cargo test --workspace --all-features --no-fail-fast --exclude=db-diesel, and cargo clippy --workspace --all-features --tests -- -D warnings; start Redis or create the SQLite database first if the crate needs one, as .github/workflows/ci.yml does. Open a pull request that links the Sentry issue, quotes the frames and the failing test output, and explains the cause. If it does not reproduce, stop and report what you tried.\n\nAlert payload:\n{payload}","resources":[{"url":"https://github.com/your-org/your-app"}],"connections":["sentry"]}