This is not

Like what you see? Install OctoLinker now!

Skip to content


Here are 4,427 public repositories matching this topic...

tiangolo commented Jun 12, 2020

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
lemarcgagnon commented Apr 14, 2021

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

To Reproduce
Steps to reproduce the behavior:

  1. Go to ''
  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.

If applicable, add screensho

panagiks commented Apr 20, 2021

🐣 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

IdemenB commented May 1, 2021

Running a query on a Postgres DB table with a field of MONEY type gives the following error with the query_as! macro. This happens despite the fact that the related field in the Struct field is set as "PgMoney" documented in

unsupported type MONEY of column #5 ("paymentamount")

Am I missing something here?


📌 TransmittableThreadLocal(TTL), the missing Java™ std lib(simple & 0-dependency) for framework/middleware, provide an enhanced InheritableThreadLocal that transmits values between threads even using thread pooling components.

  • Updated May 17, 2021
  • Java
njsmith commented May 18, 2020

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

Improve this page

Add a description, image, and links to the async topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the async topic, visit your repo's landing page and select "manage topics."

Learn more