Skip to content
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

DownloadPackage Task Fails When Trying To Get Latest Version of a Package #15022

Closed
asos-benhoward opened this issue Jul 7, 2021 · 8 comments

Comments

@asos-benhoward
Copy link

asos-benhoward commented Jul 7, 2021

Question, Bug, or Feature?
Type: Bug

Enter Task Name: DownloadPackage

Environment

Not sharing org name or project here!

  • Agent - Hosted

Issue Description

This issue relates to pull request 12334 - DownloadPackage to support latest version.

We have a feed which contains nearly 6000 packages. I'm trying to use the DownloadPackage task with "latest" as the version. The ResolveLatestVersion function appears to be using an undocumented querystring parameter that either does not exist, or does not work. The packageIdQuery parameter is ignored and the top 1000 of all packages in the feed are returned. The package I'm trying to download happens to be the 1444th package in the list and so the function fails when it can't be found as it does not appear in the first 1000 packages. I would have thought the correct uri would be this one, as at this point the packageid is known (either br resolving from package name or because the id was passed in directly).

Task logs

I'm not going to share logs here.

To Replicate

  • Create a feed with more than 1000 packages
  • Call _apis/Packaging/Feeds/[feedid]/Packages and identify which packages are not in the response
  • Try to download the latest version one of those packages using the DownloadPackage@1 task
@asos-benhoward
Copy link
Author

@evertonmc

@github-actions
Copy link

github-actions bot commented Jan 3, 2022

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

@github-actions github-actions bot added the stale label Jan 3, 2022
@asos-benhoward
Copy link
Author

This is still an issue

@github-actions github-actions bot removed the stale label Jan 3, 2022
@github-actions
Copy link

github-actions bot commented Jul 2, 2022

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

@github-actions github-actions bot added the stale label Jul 2, 2022
@bjh1977
Copy link

bjh1977 commented Jul 4, 2022

Still an issue

@github-actions github-actions bot removed the stale label Jul 4, 2022
@github-actions
Copy link

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

@github-actions github-actions bot added the stale label Dec 31, 2022
@bjh1977
Copy link

bjh1977 commented Dec 31, 2022

Still an issue

@github-actions github-actions bot removed the stale label Dec 31, 2022
@github-actions
Copy link

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants