Unable to retrive new metadata components from org browser - Salesforce - ENOENT: no such file or directory, stat 'c:\.forceignore'

[av4213]

00:52:09.951 Starting SFDX: Retrieve This Source from Org

ENOENT: no such file or directory, stat 'c:.forceignore'

[svc-idee-bot]

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]

Hello @av4213 👋 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:

• Make sure you've provided detailed steps to reproduce your issue, as well as all error messages that you see.
  • A repository that clearly demonstrates the bug is ideal.
  • Error messages can be found in the Problems Tab, Output Tab, and from running Developer: Toggle Developer Tools in the command palette.
• Make sure you've installed the latest version of the Salesforce Extension Pack for VSCode. (docs)
• Search GitHub for existing related issues.

Thank you!

[av4213]

Hi this issue has nothing to do with versions.. It is working for all other branches in my gitlab when i try to retrieve but one particular branch is having the problem.

[CristiCanizales]

Hi @av4213, we need ALL the details we ask in the issue template to be able to have some context, not just an isolated error message. Please edit your issue and provide all the details so we can help you.

[github-actions]

This issue has not received a response in 3 days. It will auto-close in 2 days unless a response is posted.

[av4213]

Salesforce Extension Version in VS Code:v62.5.1
Salesforce CLI Version: 2.51.6 win32-x64 node-v20.15.0
OS and version: Microsfot Windows 10 Enterprise and 10.0.19045 Build 19045
VS Code version: 1.95.3
Most recent version of the extensions where this was working:v62.5.1

[daphne-sfdc]

Hi @av4213, In the branch where you're seeing this issue, does this problem happen with all of the metadata types in org browser or just one particular metadata type? If it's just one type, what is that type?

[av4213]

Hi Yang, It is happening for all metadata types -- any new metadata which is in org and not there in the branch we are getting this. Thanks, Ashok

…

On Tue, Dec 10, 2024 at 10:01 AM Daphne Yang ***@***.***> wrote: Hi @av4213 <https://github.com/av4213>, In the branch where you're seeing this issue, does this problem happen with all of the metadata types in org browser or just one particular metadata type? If it's just one type, what is that type? — Reply to this email directly, view it on GitHub <#3149>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAHICOJMWINXX7MHEDWZQTL2E362XAVCNFSM6AAAAABS2TFIAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZRHEYTQMBZGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Thanks & Regards, Ashok Varma

[daphne-sfdc]

1. So in any other branch, you try to retrieve new metadata which is in org but not in branch, and it works as expected, correct?
2. In the branch which you are seeing the issue, what happens if you try to retrieve metadata which already exists in both org and branch? Are you able to re-retrieve the existing metadata?

[av4213]

1 . Yes you are right. 2. If it already exists in the branch I am able retrieve it from org no issue there. Thanks & Regards, Ashok Varma

…

On Tue, Dec 10, 2024 at 1:36 PM Daphne Yang ***@***.***> wrote: 1. So in any other branch, you try to retrieve new metadata which is in org but not in branch, and it works as expected, correct? 2. In the branch which you are seeing the issue, what happens if you try to retrieve metadata which already exists in both org and branch? Are you able to re-retrieve the existing metadata? — Reply to this email directly, view it on GitHub <#3149>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAHICOJ2VTD3RE6VBCP2NNL2E47FRAVCNFSM6AAAAABS2TFIAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZSGY4TQMRXGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[daphne-sfdc]

1. Can I get the full file path of your .forceignore file in the branch that contains the issue?
2. Can you also send me the contents of the .forceignore file?