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

Run and Debug button is blank after VSCode update #88

Closed
RaptorX opened this issue May 7, 2021 · 3 comments
Closed

Run and Debug button is blank after VSCode update #88

RaptorX opened this issue May 7, 2021 · 3 comments
Assignees
Labels
bug something isn't working

Comments

@RaptorX
Copy link

RaptorX commented May 7, 2021

Issue Type: Bug

After VSCode update the icon on the top right that is used to run a script now presents a white square.

It happens to other extensions as well

Extension version: 2.8.0
VS Code version: Code 1.56.0 (cfa2e218100323074ac1948c885448fdf4de2a7f, 2021-05-04T22:09:06.405Z)
OS version: Windows_NT x64 10.0.19042

System Info
Item Value
CPUs Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz (4 x 3200)
GPU Status 2d_canvas: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 31.45GB (24.24GB free)
Process Argv D:\Cloud\RaptorX\Dropbox\Isaias\Scripts to Work on\Drip Campaign\Drip --crash-reporter-id e2f4b83e-b638-4515-902d-f6811bd3e786
Screen Reader no
VM 0%
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30294772
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30291489
pythontb:30283811
vspre833cf:30267465
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vscorecescf:30290706
pythondataviewer:30285071
vscus158cf:30286554
bridgeflightcf:30299184

@mark-wiemer
Copy link
Collaborator

OK, this is probably an issue with VS Code itself, not the extension.

On an unrelated note @RaptorX, how did you open this issue? I've set it up to auto-assign myself for all issues created through GitHub, did you create this issue through VS Code itself?

@mark-wiemer mark-wiemer self-assigned this May 9, 2021
@RaptorX
Copy link
Author

RaptorX commented May 9, 2021

Yes, this was directly created on the feedback section of VSCode

I thought I was sending the information to the VSCode devs but it seems to be redirected to the Extension dev.
The thing is that I am sure that this is not a problem with the extension.

It started happening after a Code update.

Maybe extensions might need to conform to new standards?

@mark-wiemer btw, I am looking to modify this module a bit. Where is the location inside the vscode folder where I could find it?

I would fork this project, make the changes and then copy it to the correct location for vscode but Im not sure where that is :P

@mark-wiemer
Copy link
Collaborator

Closing this as resolved thanks to recent updates to VS Code. @RaptorX, feel free to open a discussion if you still have questions about how to modify this project and get it running locally :)

@mark-wiemer mark-wiemer added the bug something isn't working label Jun 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants