Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Whole blocks marked as unreachable #2241

Closed
vincentleeuwen opened this issue Jan 12, 2022 · 2 comments
Closed

Whole blocks marked as unreachable #2241

vincentleeuwen opened this issue Jan 12, 2022 · 2 comments

Comments

@vincentleeuwen
Copy link

vincentleeuwen commented Jan 12, 2022

Issue Type: Bug

Whole blocks of code are marked as unreachable even tough they are not. I don't even remember updating pylance or vscode or anything? Very frustrating.

Extension version: 2022.1.0
VS Code version: Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:37:28.172Z)
OS version: Darwin x64 20.5.0
Restricted Mode: No

System Info
Item Value
CPUs Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz (8 x 2300)
GPU Status 2d_canvas: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 2, 3, 3
Memory (System) 8.00GB (0.11GB free)
Process Argv --crash-reporter-id 3d2976ab-329e-4457-bcd5-1f1f5634912d
Screen Reader no
VM 0%
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
pythontb:30283811
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vscop804cf:30404767
vs360cf:30404996
vsrem710cf:30416617
py55gd98cf:30419166

Screenshot 2022-01-12 at 10 20 01

@jshaefferbfly
Copy link

jshaefferbfly commented Jan 12, 2022

This comment covers what's going on, says there will be a fix in the next release: #2224 (comment)

@heejaechang
Copy link
Contributor

it is a dup of #2224

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants