First check

• I added a very descriptive title to this issue.
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the FastAPI documentation, with the integrated search.
• I already searched in Google "How to X in FastAPI" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answ

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://react-query.tanstack.com/examples/nextjs'
2. Click on 'Nextjs SSG'
3. Scroll down to '....'
4. 502 Bad Gateaway

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screensho

🐣 Is your feature request related to a problem? Please describe.
We had a report in aiohttp-session (see aio-libs/aiohttp-session#574) that a user submitting a 'large' cookie had the cookie dropped by the receiving browser.

According to RFC 6265 - section 6.1:

General-use user agents SHOULD
provide each of the following minimum

Stitching API

Opencv provide a Stitching module/API

Bascially, i would like to be able to rewrite stitching_detailed.cpp in javascript

This includes :

• Stitcher class
• Features extractors (already implemented in opencv4nodejs)
• Estimator

I have trouble using (or understanding how to use) sqlx::Type. I have derived it for a wrapper around a String.
As far as I understand, this should implement Encode and Decode traits for the wrapper type and as a consequence I should be able to pass an instance of the wrapper type to query! macro, but I get an error stating that the drivers expects an &str instead of the wrapper type.

the current demo.gif dates back to gitui 0.7 (July 2020) and could use some refresh and maybe even some professional hand that adds some subtitles that explain what you see.

What should happen if deliver_cancel raises an exception? In the current implementation, the shielded cancel scope will prevent it from propagating until the process exits, which might take a while if the crash occurred before signaling the process in any way. Maybe on exception from a user-specified deliver_cancel we should call the default deliver_cancel to kill the process? Or just kill() since