Unexpected Behavior When Using Extensions

[hungds99]

Bug description

• When I install Prisma for VSCode I got this issue:

• Git

[error] [GitHistoryProvider][provideHistoryItems] Failed to get history items with options '{"historyItemRefs":["refs/heads/main"],"limit":50,"skip":0}': Error: spawn EBADF

• TailwindCSS:

[Error - 10:07:32 AM] Tailwind CSS IntelliSense client: couldn't create connection to server.
Error: spawn EBADF
    at ChildProcess.spawn (node:internal/child_process:420:11)
    at spawn (node:child_process:819:9)
    at fork (node:child_process:175:10)
    at Object.e.fork (node:electron/js2c/node_init:2:19269)

How to reproduce

• VSCode Git enabled

• Install Prisma ext

• Try to change code to see git show changed file but it not change

• In VSCode move to Git tab and try refresh and got the issue above

• Reload VSCode it make break some extensions

Expected behavior

Prisma information

Environment & setup

• OS:
• Editor:
• Editor version:
• Extension version:

- OS: mac
- Editor: VSCode
- Editor version: Latest

[opswiz]

Yeah Facing same issue, on quite a large project, having the extension enabled gives lots of issues, not sure why but other extensions misbehaves too. Once the extension disabled, everything is fine.

[igalklebanov]

Hey 👋

Sorry ya'll had a bad experience with the extension as of late. 🫶

Can you please try the latest insider version @ https://marketplace.visualstudio.com/items?itemName=Prisma.prisma-insider? 🤞