-
Notifications
You must be signed in to change notification settings - Fork 4.3k
fix(pipelines): can't have the same asset display name 3 times #34017
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
Conversation
When introducing friendly asset names in #33844, we made a mistake in calculating unique action names for distinct assets with the same display name. As a result, the same asset could be added to the pipeline twice, but not thrice. Fix the logic. Also in this PR: Stages can't have a name of only one character. Fix that. Closes #34004.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(This review is outdated)
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #34017 +/- ##
=======================================
Coverage 83.98% 83.98%
=======================================
Files 120 120
Lines 6976 6976
Branches 1178 1178
=======================================
Hits 5859 5859
Misses 1005 1005
Partials 112 112
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Comments on closed issues and PRs are hard for our team to see. |
When introducing friendly asset names in #33844, we made a mistake in calculating unique action names for distinct assets with the same display name.
As a result, the same asset could be added to the pipeline twice, but not thrice.
The simplest fix would have been to move the increment before the reassignment of
name:But it occurred to me that that would still lead to problems if there were actions with display names that would conflict with the numbered names in that way (e.g.,
['asdf', 'asdf', 'asdf2'], leading to action names['asdf', 'asdf2', 'asdf2']).So what we do instead is linear probing: increment a counter for every name and pick the first name that is unused.
Also in this PR: Stages can't have a name of only one character. Fix that.
Closes #34004.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license