SnapStart: Using AddAWSLambdaBeforeSnapshotRequest() and AddHttpContextAccessor() in-conjunction causes initialization failure #2069

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.

Sign up for GitHub

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

Jump to bottom

Open

1 task

budgetdevv opened this issue May 9, 2025 · 0 comments

Labels

bug needs-triage

budgetdevv commented May 9, 2025

Describe the bug

As described above. See: https://github.com/budgetdevv/AWSSnapStartBugRepro/blob/5833e924110e59d3cc574461ecf2023802a0d1dd/SnapStartBugTest/src/SnapStartBugTest/Program.cs#L14C10-L14C32

Regression Issue

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

Expected Behavior

It should be able to initialize.

Current Behavior

It fails to initialize with an exception.

Reproduction Steps

Deploy the repo @ https://github.com/budgetdevv/AWSSnapStartBugRepro into an AWS Lambda instance
Enable SnapStart
Publish a version to trigger SnapStart's snapshotting

Possible Solution

Currently I am using a custom HttpContextAccessor to circumvent this

Additional Information/Context

Do look into the stacktrace here: https://gist.github.com/budgetdevv/b1304220f2cf3921723109a53f9a82a0#file-gistfile1-txt-L32

AWS .NET SDK and/or Package version used

Targeted .NET Platform

.NET 8

Operating System and version

OSX Sonoma

budgetdevv added bug needs-triage labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment