Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
av4213 opened this issue Dec 2, 2024 · 24 comments
Open

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

av4213 opened this issue Dec 2, 2024 · 24 comments
Labels
more information required Issue requires more information or a response from the customer stale validated Version information for this issue has been validated

Comments

@av4213
Copy link

av4213 commented Dec 2, 2024

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

ENOENT: no such file or directory, stat 'c:.forceignore'
@svc-idee-bot
Copy link

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
Copy link

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
Copy link
Author

av4213 commented Dec 5, 2024

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
Copy link

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 GitHub Actions
Copy link

github-actions bot commented Dec 9, 2024

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

@github-actions github-actions bot added the stale label Dec 9, 2024
@av4213
Copy link
Author

av4213 commented Dec 9, 2024

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

@svc-idee-bot svc-idee-bot added the validated Version information for this issue has been validated label Dec 9, 2024
@daphne-sfdc
Copy link

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?

@daphne-sfdc daphne-sfdc added more information required Issue requires more information or a response from the customer and removed stale labels Dec 10, 2024
@av4213
Copy link
Author

av4213 commented Dec 10, 2024 via email

@daphne-sfdc
Copy link

  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
Copy link
Author

av4213 commented Dec 10, 2024 via email

@daphne-sfdc
Copy link

  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
Copy link
Author

av4213 commented Dec 10, 2024 via email

@daphne-sfdc
Copy link

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
Copy link
Author

av4213 commented Dec 10, 2024

image

@av4213
Copy link
Author

av4213 commented Dec 10, 2024

In other branches we have this..

**/jsconfig.json

**/.eslintrc.json

**/tsconfig.json

**/*.ts

@av4213
Copy link
Author

av4213 commented Dec 10, 2024

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

image

@daphne-sfdc
Copy link

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
Copy link
Author

av4213 commented Dec 11, 2024 via email

@mingxuanzhangsfdx
Copy link
Member

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
Copy link
Author

av4213 commented Dec 12, 2024

image

It's still the same.

@mingxuanzhangsfdx mingxuanzhangsfdx transferred this issue from forcedotcom/salesforcedx-vscode Dec 12, 2024
@mingxuanzhangsfdx
Copy link
Member

mingxuanzhangsfdx commented Dec 12, 2024 •
edited
Loading

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

@iowillhoit
Copy link
Contributor

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
Copy link
Author

av4213 commented Dec 13, 2024

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 GitHub Actions
Copy link

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

@github-actions github-actions bot added the stale label Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
more information required Issue requires more information or a response from the customer stale validated Version information for this issue has been validated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@iowillhoit @CristiCanizales @svc-idee-bot @mingxuanzhangsfdx @av4213 @daphne-sfdc