Add MapAsync for concurrent collection processing #2408

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

Draft

GarrettBeatty wants to merge 3 commits into gcbeatty/durable-parallel from gcbeatty/durable-map

Draft

Add MapAsync for concurrent collection processing #2408

net 10

GitHub Advanced Security / Semgrep OSS failed Jun 8, 2026 in 3s

6 new alerts including 6 errors

New alerts in code changed by this pull request

6 errors

See annotations below for details.

View all branch alerts.

Annotations

Check failure on line 7 in Libraries/test/Amazon.Lambda.DurableExecution.IntegrationTests/TestFunctions/MapFailureToleranceFunction/Dockerfile

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'.

Check failure on line 7 in Libraries/test/Amazon.Lambda.DurableExecution.IntegrationTests/TestFunctions/MapFirstSuccessfulFunction/Dockerfile

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'.

Check failure on line 7 in Libraries/test/Amazon.Lambda.DurableExecution.IntegrationTests/TestFunctions/MapHappyPathFunction/Dockerfile

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'.

Check failure on line 7 in Libraries/test/Amazon.Lambda.DurableExecution.IntegrationTests/TestFunctions/MapMaxConcurrencyFunction/Dockerfile

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'.

Check failure on line 7 in Libraries/test/Amazon.Lambda.DurableExecution.IntegrationTests/TestFunctions/MapPartialFailureFunction/Dockerfile

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'.

Check failure on line 7 in Libraries/test/Amazon.Lambda.DurableExecution.IntegrationTests/TestFunctions/MapReplayDeterminismFunction/Dockerfile

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'.