Skip to content

Add replay-aware logger to Amazon.Lambda.DurableExecution #2371

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

Open
GarrettBeatty wants to merge 1 commit into
base: GarrettBeatty/stack/3
Choose a base branch
from

Add replay-aware logger to Amazon.Lambda.DurableExecution

61f37ec
Select commit
Loading
Failed to load commit list.
Open

Add replay-aware logger to Amazon.Lambda.DurableExecution #2371

Add replay-aware logger to Amazon.Lambda.DurableExecution
61f37ec
Select commit
Loading
Failed to load commit list.
GitHub Advanced Security / Semgrep OSS failed May 20, 2026 in 6s

1 new alert including 1 error

New alerts in code changed by this pull request

  • 1 error

See annotations below for details.

View all branch alerts.

Annotations

Check failure on line 12 in Libraries/test/Amazon.Lambda.DurableExecution.IntegrationTests/TestFunctions/ReplayAwareLoggerFunction/Dockerfile

See this annotation in the file changed.

Code scanning / Semgrep OSS

Semgrep Finding: dockerfile.security.missing-user-entrypoint.missing-user-entrypoint Error test

By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile is a USER other than 'root'.