Raminder Singh
Raminder Singh
[Version 1.5.1](https://github.com/supabase/pg_graphql/releases/tag/v1.5.1) contains a proper performance fix for the timeouts.
`PoisonError` indicates a panic while a lock is held. See https://doc.rust-lang.org/std/sync/struct.PoisonError.html. `pg_graphql` doesn't itself use locks but one of its dependencies might. Is it on hosted platform? If yes, could...
Yes, opening a ticket would work. Mention this GH issue in it.
This is what causes this error: 1. A graphql query panics somewhere in the code called from functions which are annotated with the [cached attribute](https://docs.rs/cached/latest/cached/proc_macro/attr.cached.html). 2. Since the [annotated function...
@steve-chavez any idea what could cause the 401 error?
@SheteUC thanks for the PR. If you could fix the CI failure and tackle my review comments, I'd be happy to merge.
Thanks, I didn't realize `TlsByteVecU8` is more efficient. I should definitely use it in my work. I'll stick to the `SerializeBytes`/`DeserializeBytes` versions as they work with both `std` and `no_std`....
@franziskuskiefer a follow up question: I replaced `TlsVecU16` with `TlsByteVecU16` in my code but there is a difference in decoding. E.g. ```rust let bytes = [0, 3, 2, 1, 0];//first...
I have opened a draft PR to add support for the AppendRows api in #95. @lquerel If this looks ok, it can be merged and other APIs can be added...
Hi @point-source, We are still working on improving the docs, but to get you unblocked I will try to answer your questions here. > Do I have to assume that...