Pluriscient

Results 8 comments of Pluriscient

Crash on saving

I don't think I noticed, but my memory of the incident has faded by now.

Real cases using the template

I came across this project for anyone that this remains of interest to: https://github.com/cduvallet/microbiomeHD

Tutorial Broken Links

Additionally, in https://lalrpop.github.io/lalrpop/tutorial/001_adding_lalrpop.html the link to the tutorial is broken, as well as the link to the next section. It seems like the /tutorial/ part of the internal links are...

Tutorial Broken Links

> > > lalrpop.github.io doesn't seem to exist anymore ... https://lalrpop.github.io/lalrpop/ does so it's more a matter of redirecting to that which is not happening

Receiving warning when I'm not calling auth.getSession anywhere: Using is potentially insecure as it loads data directly from the storage medium (typically cookies) which may not be authentic. Prefer using supabase.auth.getUser() instead. To suppress this warning call supabase.auth.getUser() before you call supabase.auth.getSession()

+1 to the problem, only call getSession in the hooks.server.ts with the code from the tutorial (adapted to prevent setting cookies after request has been returned) ```js let called =...

Receiving warning when I'm not calling auth.getSession anywhere: Using is potentially insecure as it loads data directly from the storage medium (typically cookies) which may not be authentic. Prefer using supabase.auth.getUser() instead. To suppress this warning call supabase.auth.getUser() before you call supabase.auth.getSession()

> https://github.com/supabase/auth-js/blob/92fefbd49f25e20793ca74d5b83142a1bb805a18/src/GoTrueClient.ts#L936 - Here is the culprit. I just created a new issue and linked it. > > @Pluriscient - I'm not sure why you're doing that, but it doesn't...

Receiving warning when I'm not calling auth.getSession anywhere: Using is potentially insecure as it loads data directly from the storage medium (typically cookies) which may not be authentic. Prefer using supabase.auth.getUser() instead. To suppress this warning call supabase.auth.getUser() before you call supabase.auth.getSession()

> Looks like that [fix doesn't work](https://github.com/supabase/auth-helpers/issues/466#issuecomment-1727759352) YMMV, but I haven't seen a crash due to setCookies since. This error popped up the day after when we ran a fresh...

Updating to 0.1.16 from 0.1.14 broke my wrapper due to access issues to `wrappers.wrappers_fdw_stats`

Created a support request for this on the hosted version (just set up a fresh install of the stripe wrapper - twice - and this problem occurs when querying a...