[SFN] Execution of Reentrant Distributed Map States

[MEPalma]

Motivation

Currently the StepFunctions v2 interpreter is unable to execute reentrant distributed map states. This is due to a lack of end of evaluation cleanups, which means the workers activate logic does not start any new workers. This PR addresses such issue and adds relevant snapshot tests. Addresses: #10662

Changes

• Added member cleanups at the end of distributed map evaluation
• Added relevant snapshot tests

[github-actions]

LocalStack Community integration with Pro

    2 files  ±0      2 suites  ±0   1h 37m 29s ⏱️ +18s
2 932 tests +6  2 638 ✅ +4  294 💤 +2  0 ❌ ±0 
2 934 runs  +6  2 638 ✅ +4  296 💤 +2  0 ❌ ±0 

Results for commit 9f9c75d. ± Comparison against base commit 3c06fd4b.

This pull request removes 5 and adds 11 tests. Note that renamed tests count towards both.

tests.aws.services.events.test_events.TestEvents ‑ test_event_pattern
tests.aws.services.events.test_events.TestEvents ‑ test_put_event_without_source
tests.aws.services.events.test_events.TestEvents ‑ test_put_events_with_nested_event_pattern
tests.aws.services.events.test_events.TestEvents ‑ test_put_events_with_values_in_array
tests.aws.services.events.test_events.TestEvents ‑ test_put_target_id_validation

tests.aws.services.cloudformation.api.test_stacks.TestStacksApi ‑ test_update_stack_with_same_template_withoutchange_transformation
tests.aws.services.events.test_event_patterns ‑ test_event_pattern_source
tests.aws.services.events.test_events.TestEventPattern ‑ test_put_events_pattern_nested
tests.aws.services.events.test_events.TestEventPattern ‑ test_put_events_pattern_with_values_in_array
tests.aws.services.events.test_events.TestEventTarget ‑ test_put_target_id_validation
tests.aws.services.events.test_events.TestEvents ‑ test_put_events_without_source
tests.aws.services.sqs.test_sqs.TestSqsProvider ‑ test_marker_serialization_json_protocol["{\\"foo\\": \\"ba\\rr\\"}"]
tests.aws.services.sqs.test_sqs.TestSqsProvider ‑ test_marker_serialization_json_protocol[{"foo": "ba\rr", "foo2": "ba"r""}]
tests.aws.services.stepfunctions.v2.scenarios.test_base_scenarios.TestBaseScenarios ‑ test_map_state_config_distributed_reentrant
tests.aws.services.stepfunctions.v2.scenarios.test_base_scenarios.TestBaseScenarios ‑ test_map_state_config_distributed_reentrant_lambda
…

This pull request skips 1 test.

tests.aws.services.events.test_events.TestEvents ‑ test_put_event_without_detail

♻️ This comment has been updated with latest results.

[joe4dev]

LGTM 👍

I added a small suggestion for a comment to clarify the intent of the test scenarios.

[joe4dev]

Did you manually check (e.g., using SNAPSHOT_RAW=1) that we return the correct ARN in the right format here?

[MEPalma]

I can confirm we do produce the correct ARN format, and we do have tests that validate this aspect of MapRuns. However, here I decided to skip this check to avoid crowding the test state with ordering reordering logic. We can however still validate that for each map input the correct output (and events) are computed.

[joe4dev]

Reasonable. No need to double-check if we have other tests covering this part 💯