johnpapa/vscode-peacock

Stopped Working Entirely

zethon opened this issue · 21 comments

zethon commented

Versions (please complete the following information):

  • OS: mac
  • VS Code version 1.76
  • Peacock Version 4.2.2

Describe the bug
Colors don't change anymore. If I open a project that already had a specific color, the project stays that color, even if I uninstall the plugin. Reinstalling did not help. Restarting VSCode did not help.

To Reproduce

Simply install Peacock on the latest VSCode and it does not work.

Expected behavior
The plugin should work

Screenshots
I can provide video if necessary.

Additional context
None

johnpapa commented

Thank you @zethon for creating this issue!

zethon commented

On multiple computers the plugin no longer works. :(

kiranFullStack commented

I wish it just stopped working on my VS Code....because it is permanently set to s stupid green color 😡😡😡😡

kiranFullStack commented

I had to remove all colors in settings, then it got reset

Pfeil commented

Same issue here. Removing the colors from .vscode/settings.json is easy, but if I try to select a color, the list of colors will simply not appear. All other Peacock items in the menu will also not work.

The only reaction I see from selection a Peacock command, is the "Activating Extensions" spinner in the status bar. I would guess that there is an initialization issue, but I have no idea how to debug this properly.

OS: MacOS 13.2.1
VScode: 1.76.2
Peacock: v4.2.2

  • 👍1
jamiehs commented

I'm also getting the issue of having a non-functional Peacock extension.
I'm on:

  • MacOS: 12.6.3
  • VSCode: 1.77.0
  • Peacock: 4.2.2

image

Runtime Status says:

Not yet activated.

Peacock items are still in the command palette, activating them sometimes shows "Activating Extensions..." at the bottom status bar as @Pfeil stated, however the colors are not applied. Existing color themes persist obviously as they are already written to the .vscode/settings.json file.

I have tried saving a workspace explicitly instead of relying on the .vscode/settings.json file, but it makes no difference.

I have also tried deactivating, reactivating, uninstalling, and reinstalling. None of these work.

  • 👍1
zethon commented

For anyone else seeing this problem -- when I upgraded to VSCode 1.77, Peacock started working again.

  • 😕1
jamiehs commented

Unfortunately I'm on VSCode 1.77.0 and am still seeing this issue.

  • 👍2
migbash commented

Same here, just installed the extension on 1.77.0 and none of the commands work and no change is visible.

weaversam8 commented

Same here, 1.77.1 doesn't seem to improve it either.

  • 👍3
  • 😕1
jamiehs commented

How many of us have the LiveShare extension installed?
#511 (comment)

Disabling LiveShare also fixed this for me. It appears that this is likely not an issue with Peacock, or a conflict with the LiveShare extension. (in my case)

  • 👍14
athos commented

Wow, disabling LiveShare works for me too.

  • 👍3
jgbpercy commented

Yep issue was LiveShare for me as well, weird

  • 👍2
samo9789 commented

I am glad I found this post, it was the same for me, Live Share was keeping Peacock from working. Hopefully this can be sorted out and I can re-enable Live Share in the future

Thanks to the developers for this extension

  • 👍2
hedgeye-smarshall commented

Disabling LiveShare worked for me as well. Randomly started happening this week.

  • 👍2
anotherlab commented

It stopped working for me some time ago for new workspaces, works fine in older ones and I do not have Live Share installed
VS Code 1.81.0
Windows 11

If I edit the.code-workspace file and copy the settings from an older one with the folders path defined, it appears to work.

guimar86 commented

I don't have liveShare yet I still have the same issue as everyone mentioned previously:

  • Installed Peacock
  • Changed colors for a few editor windows
  • Used the option to brighten and darken some of the colors
  • Uninstalled

When I uninstalled the green still remained. Installed again and tried the "reset workspace colors " option but no change takes place, the green still remains.

@johnpapa is there a way to know which extensions could possible have conflicts so we try and disable like other people did with liveshare?

image

guimar86 commented

Profile

Hey guys, while we wait for a definitive solution I found out that using a different profile in vscode completely removes the colors set by peacock as its literally a new window. You however need to re-install all plugins you need for your development.

Official documentation

https://code.visualstudio.com/docs/editor/profiles

Vscode official youtube page

https://www.youtube.com/watch?v=QjvvqR9KyVo

gerhardvr-finclude commented

Had this issue with Peacock for a while now. Running on Windows using VSCode insiders. Disabling Live Share immediately resolved the Peacock issue for me.

Version: 1.83.0-insider (user setup)
Commit: 7b0ae6cf9d5a0c891ad1adc4da9c36c4dc453d4d
Date: 2023-09-14T05:33:44.297Z
Electron: 25.8.1
ElectronBuildId: 23779380
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.19045

  • 👍1
carlocardella commented

@guimar86 slight OT but it depends on how you create a new profile, you can choose to "inherit" settings and extensions from Default or start fresh.

Partial profiles

nader-khiari commented

I had the same issue myself and I believe it has a conflict with Live share plugin.
Try reinstalling Live Share and I think it would work fine. It worked for me anyway.

  • 👍2