-
Notifications
You must be signed in to change notification settings - Fork 32
Fix/rteco 562 jf twine incorrectly applies build properties to similar named files #331
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
# Conflicts: # artifactory/commands/python/twine.go
| `"name": {"$match": "%s*"}` + | ||
| `}]` + | ||
| `}]` + | ||
| `"$or": [%s]` + |
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.
why are we using the or and not and logical expression?
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.
Actually it can more than one files to search.
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.
I think it makes sense, it's not logical operator in aql, can we try and compare response for and vs or
artifactory/commands/python/twine.go
Outdated
| `"$or": [%s]` + | ||
| `}` | ||
| return fmt.Sprintf(itemsPart, repo, fileInitial) | ||
| sha1OrClause := strings.Join(sha1Conditions, ",") |
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.
why it this needed?
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.
Its just appending separator between sha256 for different files.
|
Please add a testcase as well for this covering this edge case. |
| `"name": {"$match": "%s*"}` + | ||
| `}]` + | ||
| `}]` + | ||
| `"$or": [%s]` + |
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.
I think it makes sense, it's not logical operator in aql, can we try and compare response for and vs or
…lies-build-properties-to-similar-named-files

What: Searching the uploaded artifacts by path instead of name