Aaron Munger
Aaron Munger
The vast majority of the failures are happening in web. The failures aren't all due to that 504 error. The one that I'm currently looking into never starts the kernel...
thanks for filing an issue. I agree that this scrolling doesn't really feel necessary
I can't get this to repro, though I do see a stutter before the output expands enough to show all the images, so there might be a race condition there....
thanks for the gif, still not repro'ing for me but we can try to look into what might cause that
new setting available to set this
Closing since this seems to behave as expected now, unless the new experiment is turned on, and I created https://github.com/microsoft/vscode-jupyter/issues/11111 for that scenario
and for the multi-root issue: https://github.com/microsoft/vscode-jupyter/issues/5185
[interactive-window] "Create Interactive Window" command does not open in the current work directory
thanks for filing the issue. I haven't been able to repro this, it always just opens with the workspace folder as the cwd. I do see something in your logs...
[interactive-window] "Create Interactive Window" command does not open in the current work directory
Although, are you saying that you expect the cwd to be `c:\Projetos\project-2`? If your setting is `${workspaceFolder}` then it should be the workspace folder, `c:\Projetos\`. Still unclear why it's going...
[interactive-window] "Create Interactive Window" command does not open in the current work directory
ah, I was just trying a workspace with two folders, not a multi-root workspace. Following the terminal's example seems reasonable to me