Skip to content

Conversation

@naveenku-jfrog
Copy link
Collaborator

@naveenku-jfrog naveenku-jfrog commented Dec 26, 2025

  • All tests passed. If this feature is not already covered by the tests, I added new tests.
  • All static analysis checks passed.
  • Appropriate label is added to auto generate release notes.
  • I used gofmt for formatting the code before submitting the pull request.
  • PR description is clear and concise, and it includes the proposed solution/fix.

What: Searching the uploaded artifacts by path instead of name

@naveenku-jfrog naveenku-jfrog added the bug Something isn't working label Dec 26, 2025
`"name": {"$match": "%s*"}` +
`}]` +
`}]` +
`"$or": [%s]` +
Copy link
Contributor

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?

Copy link
Collaborator Author

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.

Copy link
Collaborator

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

`"$or": [%s]` +
`}`
return fmt.Sprintf(itemsPart, repo, fileInitial)
sha1OrClause := strings.Join(sha1Conditions, ",")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why it this needed?

Copy link
Collaborator Author

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.

@reshmifrog
Copy link
Contributor

Please add a testcase as well for this covering this edge case.

`"name": {"$match": "%s*"}` +
`}]` +
`}]` +
`"$or": [%s]` +
Copy link
Collaborator

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
@github-actions
Copy link
Contributor

👍 Frogbot scanned this pull request and did not find any new security issues.


@naveenku-jfrog naveenku-jfrog merged commit 049e011 into jfrog:main Dec 30, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants