awslabs / awslabs/aws-lambda-cpp
LAMBDA_RUNTIME Failed to get next invocation. No Response from endpoint
- 主要語言
- C++
- 星號
- 465
- 分支
- 98
- 平均合併
- 12 小時 47 分鐘
- 30 天內合併 PR
- 3
描述
Hi guys!
I just writing some lambdas in c++ using the aws-lambda-cpp
i checking my log and i have this Error in my log:
>
[ERROR] [1553201323958] LAMBDA_RUNTIME Failed to get next invocation. No Response from endpoint
do you know if this is normal? because i check and debug my code but i don't found nothing.
what my lambda do is extract the body from SQS request, and make a slack post with the message.
for that i use curl and have the ssl disable
other thing is i dont see a print message that i have in the main after the
```
invocation_response handler(invocation_request const &req) {
return invocation_response::success();
}
```
this is my main:
```
int main() {
//use AWS namespace and libs
using namespace Aws;
//set the log for the sdk
SDKOptions options;
//init AWS API
InitAPI(options);
{
auto handler_function = [](aws::lambda_runtime::invocation_request const &req) {
return handler(req);
};
run_handler(handler_function);
}
// shutdown the aws api
std::cout << "ShutdownAPI api" << "\n";
ShutdownAPI(options);
std::cout << "exit" << "\n";
//exit
return 0;
}
```
i dont see the Shutdown and exit print in the cloud-watch log
so the question
the ShutdownAPI(options); and the return 0 is never called?
thank you!!!
貢獻指南
研究方向
從回報的 LAMBDA_RUNTIME 日誌和主要函式的 run_handler 進入點開始,接著追蹤 handler(req) 是否返回,以及在哪裡到達 ShutdownAPI。根據 runtime 的行為確認預期的生命週期,並記錄 CloudWatch 中應該顯示的內容;完成的標準是解釋清楚 endpoint 訊息和缺少的列印輸出。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- aws, cpp
- 領域
- backend, cloud
- Issue 類型
- 缺陷
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 30/100