Publishing extension via cli takes for ever
See original GitHub issuewe use
npx ovsx publish ./filename.vsix -p ***
to publish. earlier it used to work correctly, from past one week, its taking for ever. fyi, it looks like it has published extension but still process did not die/killed
refer1: https://github.com/cedric05/dothttp-runner/runs/6830285884?check_suite_focus=true#step:9:1 refer2: https://github.com/cedric05/dothttp-runner/runs/6642336794?check_suite_focus=true#step:9:2
Issue Analytics
- State:
- Created a year ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Publishing a Visual Studio extension via command line
This walkthrough shows you how to publish a Visual Studio extension to the Visual Studio Marketplace using the command line. When you add...
Read more >Publishing extensions to make them available for public use
After your extension has passed all necessary test requirements, you can publish it to make it publicly available for use through the CloudFormation...
Read more >Publishing Extensions - Visual Studio Code
Using vsce, the CLI tool for managing VS Code extensions; Packaging, publishing and unpublishing extensions; Registering a publisherId necessary for publishing ...
Read more >Publish an Azure DevOps extension from command line fails ...
I develop an Azure DevOps extension. Now I want to automate the publishing process. Here the journey begins ... Following the theory here ......
Read more >Is Your VS Code Extension Slow? Here's How to Speed it Up!
Have you ever noticed that some extensions take a few moments to initialize as you start VS Code? What might cause this delay?...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If that can help, that release was completely empty due to an issue on our side 😅 None of our actual working releases have ever completed, as far as I know
Something to note is that like the original poster says, the publishing always work, the process just never ends
Thanks @TwitchBronBron I diffed versions
0.2.0
and0.2.1
The main difference is that in version0.2.1
theExtensionProcessor
starts reading properties from the *.vsixmanifest XML file (instead of package.json) and it createsWEB__RESOURCE
FileResources
for web extensions. This most likely has a performance impact, especially creating theFileResources
.@TwitchBronBron @Princesseuh I’ll try publishing your extensions against versions 0.2.0 and 0.2.1 to see if there’s a performance difference.
git diff b2e43eb60bd8737bb41e5a99f5e45538472499c8:server/src/main/java/org/eclipse/openvsx/ExtensionProcessor.java 9a1b96483b504f1403a8e1a3e04e3abff5dda099:server/src/main/java/org/eclipse/openvsx/ExtensionProcessor.java