code-server --install-extension ms-python.python@<version> always installs the latest version #2626

Activity

1. jsjoeio

   added

   help-wanted

   needs-investigationThis issue needs to be further investigatedThis issue needs to be further investigated

   on Feb 2, 2021
2. jsjoeio commented on Feb 2, 2021

   

   jsjoeio

   on Feb 2, 2021

   Last edited by jsjoeio

   Contributor

   More actions

   Sorry for the late reply @ddurham2 - thanks for the detailed issue! I've added this to our Triage bucket and hope we can investigate soon!

   A possible workaround - you should be able to install a specific version of an extension using the VSIX file directly and the "Install from VSIX" in the Extension Menu.

   

   👍React with 👍1Reacted by Davy Durham
3. ddurham2 commented on Mar 14, 2021

   

   ddurham2

   on Mar 14, 2021

   Last edited by ddurham2

   Author

   More actions

   @jsjoeio Thanks for the info. I do hope this gets fixed soon as my other work arounds are starting to fail.

   As for installing the vsxi manually, is there a way to do that from the cli? (I'm in a Dockerfile here) I tried giving code-server --install-extension /path/to/file.vsxi but it saying it can't find the extension. The usage statement says I should be able to give it a vsxi file.

   I'm wondering if installing via vsxi file path broke for the same reason that the '@Version' syntax broke (my original problem)?

   Also, if I were to give it a vsxi file (like ms-python) which requires a dependency (like how ms-python also now depends on jupyter), should installing the vsxi from the cli automatically install dependencies?
4. tseader commented on Mar 15, 2021

   

   tseader

   on Mar 15, 2021

   Last edited by tseader

   More actions

   As for installing the vsxi manually, is there a way to do that from the cli? (I'm in a Dockerfile here) I tried giving code-server --install-extension /path/to/file.vsxi but it saying it can't find the extension. The usage statement says I should be able to give it a vsxi file.

   I'm wondering if installing via vsxi file path broke for the same reason that the '@Version' syntax broke (my original problem)?

   @ddurham2 - This is what I'm doing to install via vsix file, hope it helps!

   RUN curl -# -L -o /tmp/ms-python-release.vsix "https://github.com/microsoft/vscode-python/releases/download/2020.5.86806/ms-python-release.vsix" && \
       code-server --version && \ 
       # Below line doesn't work due to a bug that always installs latest version... working around this with vsix file install
       #code-server --install-extension ms-python.python@2020.5.86806 && \
       code-server --install-extension /tmp/ms-python-release.vsix && \
       code-server --list-extensions --show-versions
   
   # Add pre-defined user settings for convenience
   COPY user_settings.yaml /home/coder/.local/share/code-server/User/settings.json

   ❤️React with ❤️4Reacted by Joe Previte, Fernando Martinez, pchuri and Yulong
5. jsjoeio

   added this to the v3.9.3 milestone on Mar 15, 2021
6. jsjoeio

   modified the milestones: v3.9.3, On Deck on Apr 8, 2021
7. mateuszkitlas commented on May 25, 2021

   

   mateuszkitlas

   on May 25, 2021

   More actions

   I tried to workaround this with installing a manually downloaded version of this extension (or any other - this issue seems to affect all extensions) from this address:

   url = f'https://extensions.coder.com/api/publishers/{ext.publisher}/vsextensions/{ext.name}/{ext.version}/vspackage'
   

   but sadly, I get the newest version as well. This is kinda important for me to be able to download the right extensions version. Are there any updates on this issue?
8. jsjoeio commented on May 25, 2021

   

   jsjoeio

   on May 25, 2021

   Contributor

   More actions

   @mateuszkitlas have you tried manually installing it from Open VSX? See docs.
9. jsjoeio

   modified the milestones: On Deck, 3.11.0 on May 25, 2021
10. jsjoeio

    modified the milestones: 3.11.0, 3.12.0 on Jul 19, 2021
11. jsjoeio

    modified the milestones: 3.12.0, On Deck on Aug 11, 2021
12. stale commented on Feb 7, 2022

    

    staleBot

    on Feb 7, 2022

    More actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no activity occurs in the next 5 days.
13. stale

    added

    stale

    on Feb 7, 2022
14. stale

    closed this as completedon Feb 12, 2022
15. code-asher

    removed

    needs-investigationThis issue needs to be further investigatedThis issue needs to be further investigated

    on Jul 11, 2024