Open junedkhatri31 opened 8 months ago
This problem hit me too. There's not way to determine the cause of the fetch error or handle it.
I'd suggest either propogating the original error:
return {
error: fetchError,
data: null,
...
}
Or a new error encapsulating the original error in its cause
property:
return {
error: new Error("Fetch Failed", {cause: fetchError}),
...
}
Bug report
Describe the bug
When fetch function inside
PostgrestBuilder
fails. The error does not contain proper information why the fetch failed.To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Expected behavior
The error should contain clear information that the error is we are not able to verify certificate
Screenshots
If applicable, add screenshots to help explain your problem.
System information
Additional context
After spending 2 hours digging through internal library I found out that the error is self signed certificate is not being verified properly (Self signed cert is added properly in container's
/etc/ssl/certs/ca-certificates.crt
path. That is also an issue but I will deal with it separately.)The point is I found where exactly the problem is. It is in
src/PostgrestBuilder.ts
insidethen
function.res
object's error contains another error namedcause
that contains more information about the error. Which is getting lost. Because it is not getting assigned in newerror
object.