Repository navigation
refactor(fs): Improve duplicate step write error - #1664
Merged
Merged
Conversation
When two concurrent map-step invocations write to the same path, name the step and task, both colliding invocations, and the shared path, so the message points at which inputs collided rather than only stating the rule. An invocation is named by its input (string key or resource path), or by position when the key has no name. See: #1659
RandomByte
approved these changes
Oct 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When two concurrent map-step invocations write to the same path, name the step and task, both colliding invocations, and the shared path, so the message points at which inputs collided rather than only stating the rule. An invocation is named by its input (string key or resource path), or by position when the key has no name.
See: #1659