Why Your Axum Handler Never Ran: JSON Rejections and API Errors
Send malformed JSON, missing fields, and the wrong content type through an Axum router. Keep useful HTTP statuses while giving clients one error shape.
Each article starts with a backend problem and checks a repair against an executable example. Read the problem you have now, then follow the related Rust and database articles when you need more detail.
Send malformed JSON, missing fields, and the wrong content type through an Axum router. Keep useful HTTP statuses while giving clients one error shape.
Use a controlled authentication delay to see how Axum layer order changes a timeout boundary. Check both authorized and rejected requests.
Send a real SIGTERM to a small Axum process. Observe a request finishing during shutdown and a separate request reaching the shutdown deadline.
Follow an Axum request into a spawned SQLx lookup. Capture the missing span parent, then carry it explicitly with tracing::Instrument.
Exercise old and new SQLx write paths during a column migration. See why a completed backfill and a non-null check do not prove rollout compatibility.
Use two independent PostgreSQL pools and Axum routers to check session revocation. Distinguish later requests from work authorized before logout.
Keep upload publication and cleanup decisions in PostgreSQL. Exercise cancellation, a ready attachment, and a repeated delete against local file storage.
Force a stale-worker history with SQLx and PostgreSQL. Check the current lease generation in the same statement that commits the local business effect.