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

VSIX upload errors should indicate problematic filename(s) #718

Open
Alhadis opened this issue Jul 4, 2023 · 1 comment
Open

VSIX upload errors should indicate problematic filename(s) #718

Alhadis opened this issue Jul 4, 2023 · 1 comment
Assignees
Labels
bug Something isn't working triaged

Comments

@Alhadis
Copy link

Alhadis commented Jul 4, 2023

Describe the bug

This week I attempted to upload a new release of a VS Code extension (file-icons.file-icons). Each attempt was met with the same nebulous error:

Upload Error: Specified part does not exist in the package

In this case, the "specified part" turned out to be a missing LICENSE.md (something that wasn't a blocker until recently). Had the error stated which file(s) I neglected to include in the .vsix, it would've saved days of frustration.

Expected behaviour

An error message that elucidates which "specified part" is being referred to.

Desktop

  • OS: macOS 12.6.7 (Monterey), build 21G651
  • Browser: Observed with Firefox 114.0.2 (default browser); Edge exhibits the same behaviour.

Additional context

I generate this .vsix manually in lieu of using vsce.

@Alhadis Alhadis added the bug Something isn't working label Jul 4, 2023
@agr
Copy link

agr commented Jul 7, 2023

The reference to LICENSE.md exists in the package manifest for about a year (since April, 5th, 2022), but copying the file itself was added to packaging target in Makefile only couple of days ago (I'd guess as an attempt to address the publishing failure). So, this is the web site complaining (in rather unhelpful way) about a file that is declared in manifest, but missing in the package. Assuming that "2 years ago" from the screenshot is actual previous publish time, that's not a new requirement that you ran into, but a result of a change of the manifest that happened after the package was published last (a year ago).

Regardless, the message needs to be clearer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triaged
Projects
None yet
Development

No branches or pull requests

3 participants