Open EricChristensen opened 1 month ago
Hi @EricChristensen,
I was unable to reproduce this issue, maybe I am missing something. I created a fastAPI app and then added an endpoint from which I called the delete_user. And things seem to work fine.
@app.get("/delete")
async def delete_user_api():
await delete_user('<some user id>')
return {
"status": "OK",
}
Would it be possible to provide a minimal setup that reproduces this issue? Alternatively, I would also like you to add try/except around your delete call and help me with the type and msg of the exception.
I added the try catch around the delete user and printed the exception which was completely empty. Before adding the explicit
return {
"status": "OK",
}
The response we were getting was
{
"status": "GENERAL_ERROR",
"message": ""
}
Which makes sense based on the last two log lines from the error output
2024-05-15T17:19:20.330Z raise GeneralError(msg) from None
2024-05-15T17:19:20.330Z supertokens_python.exceptions.GeneralError
It looks like the even though this error occurs, the user does get successfully deleted, it just takes a little bit of time to take affect.
Where are you calling this function? In your custom application API, or in one of our overrides?
I added the try catch around the delete user and printed the exception which was completely empty. Before adding the explicit
What do you mean by before adding the explicit (return ok response)?
The response we were getting was
This is the response from the API? Our sdk does not translate GeneralException to this type of response from our APIs. GeneralExcexptions are just like python exceptions that get propagated to your app's error handler and however you deal with them, is up to you.
Maybe you can make a demo app showcasing this issue? Or post your api code here so we get clarity?
Will follow up on this by the end of the week and address your questions. We are switching over to passwordless only from email this week so I will be circling back to the delete function as part of that.
We are using the python sdk at version 0.17.0 using python version 3.11 from the public.ecr.aws/lambda/python:3.11 and running the backend SDK via a Lambda and API Gateway integration using the magnum and uvicorn.
The error logs that we are receiving when trying to call this method is:
An issue in the querier usually indicates that there was an issue from the core service, but there are no error logs from our core service for this call.
As requested by RP in discord our supertokens init is as follows:
I also tried using the latest version of the sdk and it still produced the same error.