Skip to content

No stack trace in the log when an exception occurs #213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
takahashi-shotaro-al opened this issue Jul 4, 2024 · 2 comments
Closed

No stack trace in the log when an exception occurs #213

takahashi-shotaro-al opened this issue Jul 4, 2024 · 2 comments
Labels
feature-request New feature or request

Comments

@takahashi-shotaro-al
Copy link

(at least in emulated callable functions), No stack trace in the log when an exception occurs, making it difficult to identify the cause.

>  ERROR:root:Unhandled error: list index out of range
i  functions: Finished "test" in 1998.7598480000001ms

Perhaps the stack trace is not output this line.

_logging.error("Unhandled error: %s", err)

@exaby73 exaby73 added the feature-request New feature or request label Aug 1, 2024
@exaby73
Copy link
Contributor

exaby73 commented Aug 1, 2024

Hello. Stack traces are currently not supported in Python Cloud Functions hence no stack currently

@CorieW
Copy link
Contributor

CorieW commented Dec 30, 2024

Closing as similar to #172

@CorieW CorieW closed this as completed Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants