AWS documentation says the Handler property has a max length 128 characters, but values exactly 128 characters long appear to be truncated to 127 characters in the dotnet6 Lambda runtime, and therefore fail.

[VijayasreeS]

Describe the bug

AWS documentation says the Handler property has a max length 128 characters, but values exactly 128 characters long appear to be truncated to 127 characters in the dotnet6 Lambda runtime, and therefore fail.

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

if the functionname is exact 128 then the lambda should work fine as the limit is 128.
A handler value exactly 128 characters long shouldn't be truncated and should invoke the handler method successfully.

Current Behavior

A handler value exactly 128 characters long
it truncates to 127 and produces error on func invocation: r is truncated in FunctionHandler

"errorType": "LambdaValidationException",
"errorMessage": "Unable to find method 'FunctionHandle' in type 'SSSSSSSSSSS.Services.SisSchAbsenceCreateScheduler.Handler' from assembly 'SSSSSSSSSSS.Services.LambdaSisAbsenceCreateScheduler': Found no methods matching method name 'FunctionHandle'.",

Reproduction Steps

Reproduction Steps
Create a Lambda with a handler specification that is exactly 128 characters long.
Try to invoke the function.

Possible Solution

No response

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

.Net 6

Targeted .NET Platform

.Net

Operating System and version

Windows 10 Enterprise

[ashishdhingra]

@VijayasreeS Good morning. This is a duplicate of #1642. The issue is with the Lambda runtime and we had opened an internal ticket (P109288213) with Lambda team. Please follow thread in that ticket to follow up on the backlog item they created at their end. This is not actionable from .NET SDK team.

Thanks,
Ashish

[github-actions]

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.