Skip to content

Sync Dev from Master #1876

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

Merged
merged 1 commit into from
Nov 19, 2024
Merged

Sync Dev from Master #1876

merged 1 commit into from
Nov 19, 2024

Conversation

normj
Copy link
Member

@normj normj commented Nov 19, 2024

Description of changes:
Sync dev branch with latest commits to master.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

…Support


The SnapStart support includes adding a new SnapStart.Registry package for registering and invoking hooks during the SnapStart lifecycle.

---------

Co-authored-by: Phil Asmar <phil.asmar@gmail.com>
Co-authored-by: Philippe El Asmar <53088140+philasmar@users.noreply.github.com>
Co-authored-by: Saksham Bhalla <bhallasaksham@gmail.com>
Co-authored-by: Saksham Bhalla <sakshmb@amazon.com>
Co-authored-by: Philip Pittle <ppittle@users.noreply.github.com>
}
catch (TypeLoadException ex)
{
Client.ConsoleLogger.FormattedWriteLine(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't appear to terminate or exit the call which means it will fall through where registry will be null. The following comment says no expection in calling SnapStart hooks but it looks like there could have been an exception still. Is this correct?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is correct. We wanted to support users still enabling SnapStart without updating their version of Amazon.Lambda.Core. If they have an older version of Core in the deployment bundle we will get a TypeLoadException when we try to access the registry in it. It is the awkwardness of dependencies in Lambda.

@normj normj merged commit 943862f into dev Nov 19, 2024
11 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants