forcedotcom / salesforcedx-vscode

Salesforce Extensions for VS Code
https://developer.salesforce.com/tools/vscode
BSD 3-Clause "New" or "Revised" License
943 stars 398 forks source link

Salesforce Extension Activation fails after 61.2 release #5671

Open dattakale86 opened 6 days ago

dattakale86 commented 6 days ago

Summary

After recent update of 61.2, salesforce extensions fails to activate properly on macos.

Steps To Reproduce:

Expected result

Actual result

Additional information

Salesforce Extension Version in VS Code: 61.2.1 Salesforce CLI Version: @salesforce/cli/2.47.6 darwin-arm64 node-v20.15.0 OS and version: MacOS Sonoma 14.5 VS Code version: 1.90 Most recent version of the extensions where this was working: 61.1.2

Error from vscode extension host:

2024-07-03 12:23:10.327 [error] TypeError: Cannot read properties of undefined (reading 'entries') at cloneUniqueListeners (/Users/dk/.vscode/extensions/salesforce.salesforcedx-vscode-core-61.2.1/node_modules/@salesforce/core-bundle/lib/index.js:12451:88) at Function.getInstance (/Users/dk/.vscode/extensions/salesforce.salesforcedx-vscode-core-61.2.1/node_modules/@salesforce/core-bundle/lib/index.js:12331:123) at detectCryptoVersion (/Users/dk/.vscode/extensions/salesforce.salesforcedx-vscode-core-61.2.1/node_modules/@salesforce/core-bundle/lib/index.js:13171:43) at /Users/dk/.vscode/extensions/salesforce.salesforcedx-vscode-core-61.2.1/node_modules/@salesforce/core-bundle/lib/index.js:13204:13 at Object.onGetCommandClose (/Users/dk/.vscode/extensions/salesforce.salesforcedx-vscode-core-61.2.1/node_modules/@salesforce/core-bundle/lib/index.js:12768:13) at ChildProcess. (/Users/dk/.vscode/extensions/salesforce.salesforcedx-vscode-core-61.2.1/node_modules/@salesforce/core-bundle/lib/index.js:12631:38) at ChildProcess.emit (node:events:514:28) at maybeClose (node:internal/child_process:1105:16) at Socket. (node:internal/child_process:457:11) at Socket.emit (node:events:514:28) at Pipe. (node:net:337:12)

svc-idee-bot commented 6 days ago

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

svc-idee-bot commented 6 days ago

Hello @dattakale86 :wave: It looks like you didn't provide all the required basic info in your issue.

If you haven't already, please provide the following info: Salesforce Extension Version in VS Code: Salesforce CLI Version: OS and version: VS Code version: Most recent version of the extensions where this was working:

Here's an example of a set of required info that will pass the validation: Salesforce Extension Version in VS Code: 60.13.0 Salesforce CLI Version: @salesforce/cli/2.42.6 darwin-arm64 node-v18.18.2 OS and version: MacOS Sonoma 14.5 VS Code version: 1.89.1 Most recent version of the extensions where this was working: 60.11.0

A few more things to check:

Thank you!

dattakale86 commented 6 days ago

Added missing required information.

peternhale commented 6 days ago

@dattakale86 Thank for reporting this issue. Try these steps:

dattakale86 commented 6 days ago

Hey @peternhale, I already tried that but it didn't help.

git2gus[bot] commented 6 days ago

This issue has been linked to a new work item: W-16159672

peternhale commented 6 days ago

@dattakale86 while we investigate this issue, I would recommend installing v61.1.2 of the extensions. I apologize for the inconvenience.

diyer commented 6 days ago

@dattakale86 Our sincere apologies for the inconvenience. can you please confirm if downgrading the version of extensions has unblocked you?

peternhale commented 6 days ago

@dattakale86 The bug has been identified in one of dependencies and is being fixed. We hope to have this issue wrapped up by middle of next week.

Would you mind providing the list of vscode extensions you are using and those that are active in your project workspace?

peternhale commented 6 days ago

One more ask

In a terminal

dattakale86 commented 5 days ago

@diyer yes downgrading salesforce cli integration plugin to previous version helped.

@peternhale I have Salesforce Extension Pack (Expanded) in my project worrkspace and output of command you asked to run:

./salesforce.salesforcedx-vscode-apex-61.1.2/node_modules/@salesforce/core/package.json: "name": "@salesforce/core", ./salesforce.salesforcedx-vscode-apex-61.1.2/node_modules/@salesforce/source-deploy-retrieve/node_modules/@salesforce/core/package.json: "name": "@salesforce/core", ./salesforce.salesforcedx-vscode-apex-61.1.2/node_modules/@salesforce/source-deploy-retrieve/package.json: "@salesforce/core": "^7.4.1", ./salesforce.salesforcedx-vscode-apex-61.1.2/node_modules/@salesforce/source-tracking/package.json: "@salesforce/core": "^7.3.9", ./salesforce.salesforcedx-vscode-apex-61.1.2/package.json: "@salesforce/core": "7.3.10", ./salesforce.salesforcedx-vscode-core-61.1.2/node_modules/@salesforce/core/package.json: "name": "@salesforce/core", ./salesforce.salesforcedx-vscode-core-61.1.2/node_modules/@salesforce/source-deploy-retrieve/package.json: "@salesforce/core": "^7.3.9", ./salesforce.salesforcedx-vscode-core-61.1.2/node_modules/@salesforce/source-tracking/package.json: "@salesforce/core": "^7.3.9", ./salesforce.salesforcedx-vscode-core-61.1.2/node_modules/@salesforce/templates/package.json: "@salesforce/core": "^7.3.10", ./salesforce.salesforcedx-vscode-core-61.1.2/package.json: "@salesforce/core": "7.3.10", ./salesforce.salesforcedx-vscode-core-61.2.1/node_modules/@salesforce/templates-bundle/package.json: "@salesforce/core-bundle": "^7.3.10" ./salesforce.salesforcedx-vscode-core-61.2.1/node_modules/@salesforce/core-bundle/package.json: "name": "@salesforce/core-bundle",

Thanks!

dvon88 commented 1 day ago

I have this same issue, downgrading does not work. My system and installation specs are the same as OP. This has now happened with two releases in a row (61.2 and 61.1.2)

peternhale commented 1 day ago

@dattakale86 @dvon88 We have identified the issue with a dependency and are working to resolve it.