I can confirm I don't see any issues anymore with:

Version: 1.55.2
Commit: 3c4e3df9e89829dce27b7b5c24508306b151f30d
Date: 2021-04-13T09:36:32.643Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Darwin x64 20.3.0

Thank you @karthiknadig and @MetRonnie , I'm using Pylance and can confirm that this microsoft/pylance-release#882 is the issue

@ParteekSJ nothing you have to do. This is something the Jupyter extension now does internally.

Thank you.

@rchiodo Just FYI - I looked into the six "most trending" extensions on the marketplace and their related GitHub release pages:

• vscode-python: publishes the VSIX files in GitHub releases (see https://github.com/microsoft/vscode-python/releases)
• vscode-cpp: publishes the VSIX files in GitHub releases (see https://github.com/microsoft/vscode-cpptools/releases)
• vscode-eslint: publishes the VSIX files in GitHub releases (see https://github.com/microsoft/vscode-eslint/releases)
• prettier-vscode: publishes the VSIX files in GitHub releases (see https://github.com/prettier/prettier-vscode/releases)
• vscode-live-server: publishes the VSIX files in GitHub releases (see https://github.com/ritwickdey/vscode-live-server/releases)
• vscode-jupyter: does not publish the VSIX files in GitHub releases (see https://github.com/microsoft/vscode-jupyter/releases)

Do you notice anything? ;-)

I was told this is an editor issue: https://github.com/JuliaLang/julia/issues/35866 (copy below)

Syntax highlighting for function names with a \partial symbol "∂" (and some other unicode characters) seems to be broken:

# broken:
function ∂f∂var() end # only var is highlighted 
function ∑vars() end # ∑ is not highlighted
function is⊥() end # nothing is highlighted

# works:
function ΔfΔvar() end
function δfδvar() end
function dfdvar() end

GitHub apparently also has some issues highlighting correctly, but for me using VS code and Julia 1.4 ΔfΔvar is highlighted correctly whereas ∂f∂var is not. I had the same issue before when using Atom.

Seems like this is fixed now, thanks!

<!-- Please search existing issues to avoid creating duplicates. -->

Environment data

• VS Code version: 1.55.2 (Universal)
• Extension version (available under the Extensions sidebar): v2021.4.765268190
• OS and version: macOS Big Sur 11.2.3 (20D91)
• Python version (& distribution if applicable, e.g. Anaconda): 3.9.2
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
• Relevant/affected Python packages and their versions:
• Relevant/affected Python-related VS Code extensions and their versions: X
• Value of the python.languageServer setting: Microsoft

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]

Expected behaviour

type "g" as normal in editor

Actual behaviour

status bar reports

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

1. Install python extension
2. open editor
3. type "g"

<!-- Note: If you think a GIF of what is happening would be helpful, consider tools like https://www.cockos.com/licecap/, https://github.com/phw/peek or https://www.screentogif.com/ . -->

Logs

Nothing

<details>

<summary>Output for <code>Python</code> in the <code>Output</code> panel (<code>View</code>→<code>Output</code>, change the drop-down the upper-right of the <code>Output</code> panel to <code>Python</code>) </summary>

<p>

XXX

</p> </details>

fixed by erase all vscode files and reinstall the extension

Unfortunately it seems like I am having the same issue. I am running Python 3.8.8 with anaconda.

Only ctrl+shift+space shows the documentation in .ipynb files and not hover. In normal .py files documentation on hover works. Version: 1.56.0-insider (user setup) Commit: 7ce1499d9541ba2acf66cd30a9054bd7818a8f80 Date: 2021-04-22T05:13:14.711Z Electron: 12.0.4 Chrome: 89.0.4389.114 Node.js: 14.16.0 V8: 8.9.255.24-electron.0 OS: Windows_NT x64 10.0.19042 Python v2021.4.765268190 Jupyter v2021.6.770905982 Python insider channel set to daily (Is there a way to see if it actually downloaded it?)

For normal VS Code the problem is even bigger, not even ctrl+shift+space works for .ipynb. Documentation works normally for .py as well. Version: 1.55.2 (user setup) Commit: 3c4e3df9e89829dce27b7b5c24508306b151f30d Date: 2021-04-13T09:35:57.887Z Electron: 11.3.0 Chrome: 87.0.4280.141 Node.js: 12.18.3 V8: 8.7.220.31-electron.0 OS: Windows_NT x64 10.0.19042 Python v2021.4.765268190 Jupyter v2021.5.745244803

Any ideas?

<!-- Please search existing issues to avoid creating duplicates. -->

Environment data

• VS Code version: 1.55.2 (Universal)
• Extension version (available under the Extensions sidebar): v2021.4.765268190
• OS and version: macOS Big Sur 11.2.3 (20D91)
• Python version (& distribution if applicable, e.g. Anaconda): 3.9.2
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
• Relevant/affected Python packages and their versions:
• Relevant/affected Python-related VS Code extensions and their versions: X
• Value of the python.languageServer setting: Microsoft

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]

Expected behaviour

type "g" as normal in editor

Actual behaviour

status bar reports

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

1. Install python extension
2. open editor
3. type "g"

<!-- Note: If you think a GIF of what is happening would be helpful, consider tools like https://www.cockos.com/licecap/, https://github.com/phw/peek or https://www.screentogif.com/ . -->

Logs

Nothing

<details>

<summary>Output for <code>Python</code> in the <code>Output</code> panel (<code>View</code>→<code>Output</code>, change the drop-down the upper-right of the <code>Output</code> panel to <code>Python</code>) </summary>

<p>

XXX

</p> </details>

basically, if it's python, we consider it a debuggable subprocess

Wooah! You gave me the hint I needed!

I was spawning directly another binary to workaround https://github.com/microsoft/vscode-python/issues/14222, but with https://github.com/copier-org/copier/pull/384 now I can execute copier as a module.

So, I changed the spawn code to spawn like [sys.executable, "-mcopier", "copy", str(src), str(dst)], and it works! I can debug subprocesses out of the box!

Thanks!

Now I'm not sure if there's still something to do regarding this issue. Maybe some docs on this subject? Or maybe inspecting the shebang of the executable to know if it's a python subprocess to be debugged?

Thank you very much @karthiknadig !

After trying a lot of actions, your suggestion solved the issue for me !

Suggestion is here.

Adding to the list of issues on the false positives of "possible method call error." I've checked the others and I don't think this one falls into any of the other categories of reported issues. If I'm wrong, please correct me.

This got fixed by https://github.com/julia-vscode/StaticLint.jl/pull/272. The fix will be in the next release.

Yeah. We have a fix for this on master but in no released version yet, afaict.

Adding to the list of issues on the false positives of "possible method call error." I've checked the others and I don't think this one falls into any of the other categories of reported issues. If I'm wrong, please correct me.

Codecov Report

Merging #5593 (759e9fa) into main (70a6e7b) will decrease coverage by 0%. The diff coverage is n/a.

@@          Coverage Diff           @@
##            main   #5593    +/-   ##
======================================
- Coverage     72%     72%    -1%     
======================================
  Files        402     402            
  Lines      26724   26724            
  Branches    3899    3899            
======================================
- Hits       19453   19261   -192     
- Misses      5638    5838   +200     
+ Partials    1633    1625     -8     

Hi,

The Issue is marked as closed. I am using the following version:

Version: 1.55.2
Commit: 3c4e3df9e89829dce27b7b5c24508306b151f30d
Date: 2021-04-13T09:37:02.931Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Linux x64 5.11.0-7612-generic

The font of markdown cells are still in monospace and are not picked from markdown font settings.

@greazer Are you referring to Improved markdown editing > Preview todo item which will implement this change? If yes then we can track that item.

Bumps actions/github-script from v3 to v4.0.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/github-script/releases">actions/github-script's releases</a>.</em></p> <blockquote> <h2>Fix "require" search path</h2> <p>Previously, the wrapped <code>require</code> searched the existing <code>module.paths</code> and <em>then</em> <code>process.cwd()</code>. We now only search <code>process.cwd()</code>. See <a href="https://github-redirect.dependabot.com/actions/github-script/pull/136">actions/github-script#136</a> for details.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions/github-script/commit/85e88a66eaa831097093a3d278536947f2984d20"><code>85e88a6</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/actions/github-script/issues/136">#136</a> from actions/search-cwd-first</li> <li><a href="https://github.com/actions/github-script/commit/5cbb702e24d65c8ebafd6aa4a1dff5a2e7c5a0d7"><code>5cbb702</code></a> v4.0.1</li> <li><a href="https://github.com/actions/github-script/commit/1ef7fd09cae454dd85632525cb815e8260f7517b"><code>1ef7fd0</code></a> Remove require search fallback</li> <li><a href="https://github.com/actions/github-script/commit/a49bf6b2cd2d19d7353cf281ec5f195f17a57cd6"><code>a49bf6b</code></a> Search the cwd first, then existing module paths</li> <li><a href="https://github.com/actions/github-script/commit/95fb649573b4020d9a24b4480947c1746afcb137"><code>95fb649</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/actions/github-script/issues/135">#135</a> from actions/wrap-require</li> <li><a href="https://github.com/actions/github-script/commit/2923e50f2900cc87d1480ca89c5058b1b9bb4c4e"><code>2923e50</code></a> Run build script</li> <li><a href="https://github.com/actions/github-script/commit/b616178d6da5de6da31a1a601c15fbcba8e5d115"><code>b616178</code></a> Merge branch 'wrap-require' of <a href="https://github.com/actions/github-script">https://github.com/actions/github-script</a> into ...</li> <li><a href="https://github.com/actions/github-script/commit/c758586ea188048eb04fe9297138b77740ac3523"><code>c758586</code></a> v4.0.0</li> <li><a href="https://github.com/actions/github-script/commit/256da4ea4d14f7090616071be552b0b2c1df5bf8"><code>256da4e</code></a> Update src/wrap-require.ts</li> <li><a href="https://github.com/actions/github-script/commit/5ee517dae8a89d8f425c220d4c8b79151bb7ff02"><code>5ee517d</code></a> Workflow syntax error</li> <li>Additional commits viewable in <a href="https://github.com/actions/github-script/compare/v3...85e88a66eaa831097093a3d278536947f2984d20">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

For #5309

If the slice panel is initally collapsed and then is expanded by the user, the bottom ~4 rows are cut off because the SlickGrid grid height is manually calculated and set, and the grid isn't aware that neighboring elements have increased in height. The solution here is to tell the grid to resize itself.

<!-- If an item below does not apply to you, then go ahead and check it off as "done" and strikethrough the text, e.g.: - [x] ~Has unit tests & system/integration tests~ -->

• [x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
• [x] Title summarizes what is changing.
• [x] Has a news entry file (remember to thank yourself!).
• [x] Appropriate comments and documentation strings in the code.
• [x] ~Has sufficient logging.~
• [x] ~Has telemetry for enhancements.~
• [x] ~Unit tests & system/integration tests are added/updated.~
• [x] ~Test plan is updated as appropriate.~
• [x] ~package-lock.json has been regenerated by running npm install (if dependencies have changed).~