morgan
08/18/2021, 9:22 AMauth.signIn()
with a none existing email for the magic link. An error 500 is returned Database error saving new user'
Just double checking if this a bug error message? I don't think users should attempted to be saved using the signIn functionsEvostance
08/18/2021, 10:05 AMjson
{
"live": false,
"notificationItems": [
"NotificationRequestItem": {
"eventDate": "2021-08-09T14:19:49+02:00"
}
]
}
Trying to figure out how to order it as its inside an array, but the array item only ever contains 1 item. Assuming I need to convert it somehow but unsure how to do this?
js
.order("data->notificationItems->NotificationRequestItem->eventDate", {
ascending: false,
});
Yggdrasill
08/18/2021, 11:16 AMGandalfG
08/18/2021, 11:57 AMburggraf
08/18/2021, 1:26 PMCartiers
08/18/2021, 6:54 PMjs
const { data: user, error } = await supabase.auth.api.getUser(
req.cookies["sb:token"]
);
I would like to add the users access token returned by the provider as i need it to interact with Discords APIjon114
08/18/2021, 8:04 PMAuthSession.makeRedirectUri({ useProxy: false })
?jon114
08/18/2021, 8:05 PMMarky
08/18/2021, 9:48 PMconst { data, error } = await this.database.rpc('boostPool', {
pool_name: pool,
amount: Number(newBoost)
})
function public.boostPool(amount => text, pool_name => text) does not exist
Marky
08/18/2021, 9:53 PMconsole.log(typeof quantity)
number
santnorm
08/18/2021, 10:14 PMjordan801
08/18/2021, 10:27 PM{
"message": "An invalid response was received from the upstream server"
}
I found in the logs that a migration was failing. It was trying to create the column confirmed_at on the auth.users table. But it already existed. So I nuked the column, allowing the migration to happily go on its way.
BUT THEN! I had a new issue. When I attempt to login using Azure auth I get a new error message: permission denied for table audit_log_entries
. Ok so I browse my users and permissions and I see that there's only 1 user, the user made by supabase. I attempt to manipulate the table via postgres client. It works fine. Hmf. Dead end. I try granting permission to the user, you know, just in case. No change. So, what user is it trying to manipulate this table with, how did it get this user, and how do I fix it? Also, how did all of this happen?
For anyone who may find this in the future. The issue is my backup manipulating the auth schema. Exclude the auth schema from backups unless you know what you're doing 😄MrWolf
08/19/2021, 3:14 AMlarryM
08/19/2021, 5:03 AMlarryM
08/19/2021, 5:34 AMPeanut
08/19/2021, 5:40 AMMarky
08/19/2021, 5:42 AMMarky
08/19/2021, 5:42 AMPeanut
08/19/2021, 5:44 AMPeanut
08/19/2021, 5:48 AMMarky
08/19/2021, 5:55 AMMarky
08/19/2021, 5:55 AMPeanut
08/19/2021, 7:30 AMPeanut
08/19/2021, 7:30 AMMarky
08/19/2021, 8:09 AMMarky
08/19/2021, 8:09 AMsoedirgo
08/19/2021, 9:46 AMCREATE FUNCTION
etc.) are exactly the Postgres-speak for "stored procedures", though technically there's also CREATE PROCEDURE
that's less commonly used.user
08/19/2021, 11:32 AMuser
08/19/2021, 11:32 AMyurix
08/19/2021, 11:34 AM