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?

[av4213]

Hi , 1. C:\Users\asaripalli\Desktop\Shift4R1&R2\12102024\phx-salesforce 2. [image: image.png] Is there a way we can connect online via call, so that i can show you the issue? Thanks, Ashok

…

On Tue, Dec 10, 2024 at 4:10 PM Daphne Yang ***@***.***> wrote: 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? — Reply to this email directly, view it on GitHub <#3149>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAHICOKIZK5BS4UKJJ6E6LL2E5KFBAVCNFSM6AAAAABS2TFIAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZSHA4TQMZVHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Thanks & Regards, Ashok Varma

[daphne-sfdc]

Hi @av4213, We're not able to meet with you via video call, but we'll be happy to continue helping you here on Github.

1. Assuming your project is called phx-salesforce - the .forceignore looks like it's in the correct location in your project.
2. I'm unable to see the image. Can you try replying directly from Github instead of via email?
3. Are the contents of the .forceignore the same for other branches that do work?

[av4213]

[av4213]

In other branches we have this..

**/jsconfig.json

**/.eslintrc.json

**/tsconfig.json

**/*.ts

[av4213]

I even tried this.. copied the content of forceingnore in this branch and tried to retrieve. but still the same.

[daphne-sfdc]

Can you please update your CLI to the latest version, if you are able? It’s sf update or npm update @salesforce/cli --global depending on how you installed it.

[av4213]

I updated the CLI but it's still the same. ***@***.*** MINGW64 ~/Desktop/Shift4R1&R2/12102024/phx-salesforce (PHXR1-PRODMaster) $ sf update (node:14900) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead. (Use `node --trace-deprecation ...` to show where the warning was created) @salesforce/cli: Updating CLI... already on version 2.68.6-950de56 # Release notes for 'sf': ## 2.68.6 (December 4, 2024) [stable] * NEW: (BETA) Open an agent in the Agent Builder UI with the new open org agent command. Use the --name flag to open an agent using its API name. For example: sf open org agent --name Coral_Cloud_Agent To find the agent's API name, go to Setup in your org and navigate to the agent's details page. (plugin-org PR forcedotcom/salesforcedx-vscode#1264 ( salesforcecli/plugin-org#1264)) * FIX: We improved the table output when project deploy start fails due to an metadata validation error. We now provide the name of the metadata type that's causing the error in the Type column. (GitHub issue forcedotcom/cli#966 ( #3110), plugin-deploy-retrieve PR forcedotcom/salesforcedx-vscode#1217 (salesforcecli/plugin-deploy-retrieve#1217)) * FIX: If you set your target-org configuration variable to a sandbox, and then run org delete scratch without specifying the --target-org flag, the command now returns an error. Previously the command would delete the sandbox. (GitHub issue forcedotcom/salesforcedx-vscode#3058 (#3058), plugin-org PR forcedotcom/cli#78 (salesforcecli/plugin-org#1257))

…

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- * Run sf whatsnew to manually view the current release notes. * You can also view them on GitHub by visiting the forcedotcom/cli ( https://github.com/forcedotcom/cli/tree/main/releasenotes) repo. * Silence notes by setting the SF_HIDE_RELEASE_NOTES env var to true. * Hide this footer by setting the SF_HIDE_RELEASE_NOTES_FOOTER env var to true.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ***@***.*** MINGW64 ~/Desktop/Shift4R1&R2/12102024/phx-salesforce (PHXR1-PRODMaster) $ git fetch --all remote: Enumerating objects: 628, done. remote: Counting objects: 100% (517/517), done. remote: Compressing objects: 100% (134/134), done. remote: Total 312 (delta 222), reused 186 (delta 116), pack-reused 0 Receiving objects: 100% (312/312), 159.62 KiB | 4.43 MiB/s, done. Resolving deltas: 100% (222/222), completed with 52 local objects. From https://git.shift4payments.com/phoenix/salesforce/phx-salesforce b694487b5..b08bf3600 PHXR1-PRODMaster -> origin/PHXR1-PRODMaster 230cd472d..4cbb87d6c PHX-Merged-R2 -> origin/PHX-Merged-R2 8d9281d1e..d507e0042 PHX-UAT -> origin/PHX-UAT edb1b5945..55fb7633e PhoenixDEV -> origin/PhoenixDEV 8883fe9a3..9f22c0a43 TempDev-V2 -> origin/TempDev-V2 * [new branch] bug/PHX-12450_Test-Class-Review-and-Update_-AccountabilityScoreSSpecialist_Test_and_-AccountabilityScoreSS_Test -> origin/bug/PHX-12450_Test-Class-Review-and-Update_-AccountabilityScoreSSpecialist_Test_and_-AccountabilityScoreSS_Test * [new branch] cherry-pick-9f22c0a4 -> origin/cherry-pick-9f22c0a4 * [new branch] cherry-pick-c8d19905 -> origin/cherry-pick-c8d19905 * [new branch] cherry-pick-ed8042b5 -> origin/cherry-pick-ed8042b5 * [new branch] feature/PHX-12013-migration-fields -> origin/feature/PHX-12013-migration-fields * [new branch] feature/PHX-12013-migration-fields-prod -> origin/feature/PHX-12013-migration-fields-prod * [new branch] feature/Phx-11911flow -> origin/feature/Phx-11911flow ***@***.*** MINGW64 ~/Desktop/Shift4R1&R2/12102024/phx-salesforce (PHXR1-PRODMaster) $ Sfdx project retrieve start -x package.xml (node:10396) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead. (Use `node --trace-deprecation ...` to show where the warning was created) Error (ENOENT): ENOENT: no such file or directory, stat 'C:\.forceignore' ***@***.*** MINGW64 ~/Desktop/Shift4R1&R2/12102024/phx-salesforce (PHXR1-PRODMaster) $

On Tue, Dec 10, 2024 at 5:47 PM Daphne Yang ***@***.***> wrote: Can you please update your CLI to the latest version, if you are able? It’s sf update or npm update @salesforce/cli --global depending on how you installed it. — Reply to this email directly, view it on GitHub <#3149>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAHICON4LMN7CO5WZ3SZ5ZT2E5VRPAVCNFSM6AAAAABS2TFIAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZTGEYTMNZXGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Thanks & Regards, Ashok Varma

[mingxuanzhangsfdx]

Hi @av4213 , could you please try to retrieve metadata with the sf cli command by following the instruction here? Please let us know the results.

[av4213]

It's still the same.

[mingxuanzhangsfdx]

Hi @av4213 , the issue seems from the libraries in cli, and I just transferred to the cli team.

[iowillhoit]

Can you please run the retrieve command with the --dev-debug flag and provide the full output? Please attach it as a file so the formatting is clean.

Also, are there any significant differences between a working branch and the failing one? You could use git diff to compare.

[av4213]

Hi, sure will provide with the flag.

Yes there are significant differences because one is prod branch (not working) and other branch is UAT & QA branch (working)

[github-actions]

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