You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm raising https_fn.HttpsError with various code=https_fn.FunctionsErrorCode.XYZ from within an @https_fn.on_request()-decorated function to test error paths. But if I throw e.g. ostensibly a 400 (FunctionsErrorCode.NOT_FOUND) the caller gets a 500. It doesn't matter what type of error I throw. Is this intentional for on_request? I'd love to have more granular HTTP errors.
Anyway, thanks very much for a lovely Python3 SDK for FB Functions - it's a super convenient service.
The text was updated successfully, but these errors were encountered:
For reference, I'm expecting the behavior described in this doc. Maybe I misread it... I'll give it another close reading but I figured it's good to get this reported.
Yeah interestingly enough @https_fn.on_call handles the error codes as I'd expect. It's odd to see the ∆ between on_call and on_request error handling.
Hello @ekalosak. Could you provide a short code sample that I may use to reproduce this issue? Also, do include the contents of your requirements.txt and python version as well.
I'm raising
https_fn.HttpsError
with variouscode=https_fn.FunctionsErrorCode.XYZ
from within an@https_fn.on_request()
-decorated function to test error paths. But if I throw e.g. ostensibly a 400 (FunctionsErrorCode.NOT_FOUND
) the caller gets a 500. It doesn't matter what type of error I throw. Is this intentional foron_request
? I'd love to have more granular HTTP errors.Anyway, thanks very much for a lovely Python3 SDK for FB Functions - it's a super convenient service.
The text was updated successfully, but these errors were encountered: