microsoft / vscode-jupyter

VS Code Jupyter extension
https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter
MIT License
1.29k stars 291 forks source link

Almost Not Useable #7710

Closed PCJimmmy closed 3 years ago

PCJimmmy commented 3 years ago

Issue Type: Performance Issue

Been almost a year since I last used VS Code.

The changes you have made are terrible. Not sure who your target audience is, but guess its not me.

Almost impossible to use.

  1. Cannot open files on a connected home server (root only). I used this server 100% of the time a year ago.
  2. Apprently VS opens in a world igrnorant of Anaconda - so it cannot find any libaries.
  3. The Jupyter extension is a joke. Getting Find and Replace to work was a 20 minute task. No idea how I really got it working.

Go searching for a new job - casue the one you have is going to dry up and go away at the rate your killing it.

VS Code version: Code 1.59.0 (379476f0e13988d90fab105c5c19e7abc8b1dea8, 2021-08-04T23:13:20.182Z) OS version: Linux x64 5.11.0-25-generic snap Restricted Mode: No

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 x 3600)| |GPU Status|2d_canvas: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
rasterization: disabled_software
skia_renderer: enabled_on
video_decode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|0, 1, 1| |Memory (System)|62.74GB (57.28GB free)| |Process Argv|--no-sandbox --force-user-env --unity-launch --crash-reporter-id b7d88903-b1c6-432b-97cb-7b5413c276a3| |Screen Reader|no| |VM|0%| |DESKTOP_SESSION|ubuntu| |XDG_CURRENT_DESKTOP|Unity| |XDG_SESSION_DESKTOP|ubuntu| |XDG_SESSION_TYPE|x11|
Process Info ``` CPU % Mem MB PID Process 0 128 8311 code main 0 0 8313 zygote 0 193 8338 gpu-process 0 0 8314 zygote 1 64 8965 window (Issue Reporter) 0 0 8345 utility 2 128 8454 shared-process 0 64 8476 ptyHost 0 0 8854 /usr/bin/bash 0 0 8987 /bin/sh -c /usr/bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command= 0 0 8988 /usr/bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command= 0 193 8595 window (OPTIVER - Visual Studio Code) 0 128 8622 extensionHost 0 128 8792 electron_node bundle.js 0 64 8637 watcherService 0 64 8715 searchService ```
Workspace Info ``` | Window (OPTIVER - Visual Studio Code) | Folder (OPTIVER): 536 files | File types: parquet(226) ipynb(46) pkl(11) csv(6) tsv(3) tfevents(2) | py(2) pyc(1) log(1) json(1) | Conf files:; ```
Extensions (3) Extension|Author (truncated)|Version ---|---|--- python|ms-|2021.8.1105858891 vscode-pylance|ms-|2021.8.0 jupyter|ms-|2021.8.1195043623
A/B Experiments ``` vsliv368cf:30146710 vsreu685:30147344 python383:30185418 pythonvspyt602:30300191 vspor879:30202332 vspor708:30202333 vspor363:30204092 pythonvspyt639:30300192 pythontb:30283811 pythonptprofiler:30281270 vshan820:30294714 vstes263cf:30335440 pythondataviewer:30285071 pythonvsuse255:30340121 vscod805:30301674 pythonvspyt200:30340761 vscextlangct:30333562 binariesv615:30325510 pythonvssor306:30344512 bridge0708:30335490 vstre464:30346472 ```
gjsjohnmurray commented 3 years ago

Please review https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions#writing-good-bug-reports-and-feature-requests

In particular, one issue per problem.

DonJayamanne commented 3 years ago

@PCJimmmy I'm so sorry for not getting back to you, and sorry you are running into these issues. We've made a lot of improvements and fixes recently when dealing with conda environments.

Cannot open files on a connected home server (root only). I used this server 100% of the time a year ago.

Please could you provide more information about this issue.

Apprently VS opens in a world igrnorant of Anaconda - so it cannot find any libaries.

Please could you provide the logs from your Jupyter output panel.

Getting Find and Replace to work was a 20 minute task. No idea how I really got it working.

Sorry about this, please could confirm this issue still persists.

DonJayamanne commented 3 years ago

Closing this issue as its been over 4 weeks, since the information was requested. We'll be happy to reopen the issue when the requested information has been provided.