GCP Cloud Functions 不再使用回溯正确分类错误

GCP Cloud Functions no longer categorizes errors correctly with tracebacks(GCP Cloud Functions 不再使用回溯正确分类错误)

问题描述

我已经使用 Cloud Functions 一年多了，在过去一个月左右的时间里，发生了一些变化，使得排错问题变得更加困难.

I've been using Cloud Functions for over a year now and in the last month or so, there's been a change that's made it much more difficult to troubleshoot errors.

以前，像下面这样简单的事情会在 Logging 中生成一个 Error，带有违规的行号和回溯(KeyError: 'test' 这里)，但现在 Logging只是显示函数执行花费了 X 毫秒，以状态完成:'crash' 归类于 Debug.

Previously, something as simple as the following would generate an Error in Logging with the offending line number and traceback (KeyError: 'test' here), but now Logging just shows Function execution took X ms, finished with status: 'crash' categorized under Debug.

def hello_world(request):
    request_json = request.get_json()
    print(request_json)
    print(request_json['test'])
    return f'Hello World!'

是否有人对发生的事情有任何见解，以及如何继续对云功能进行故障排除以及未来发生崩溃的建议?提前谢谢！

Does anybody have any insights on what happened, and advice on how to proceed to troubleshoot Cloud Functions with crashes going forward please? Thank you in advance!

推荐答案

@chengineer 在评论区提供了答案，此问题影响了 Cloud Functions，目前正在修复中.以下更新将发布在 https://issuetracker.google.com/issues/155215191.

@chengineer provided the answer in the comment thread, this issue affected the Cloud Functions and it is currently under fix. The following updates will be posted on https://issuetracker.google.com/issues/155215191.

这篇关于GCP Cloud Functions 不再使用回溯正确分类错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持编程学习网！