Federico Giust

The issue about the Test level in Prod has been there for a while now. If I use change sets, it doesn't run the tests when there is no apex...

Hi @WillieRuemmele Here's a short video demo of the issue If I do right click on VS Code and deploy to Prod, works correctly (If I'm deploying Apex it runs...

Any progress on this one? I'm having the same issue on Windows, this issue it seems that is preventing the Prettier formatter to be able to run.   Prettier...

Here's the error when I do the git pull complaining about windows-foreground-love  I use cursor.sh as my ide and have configured cursor as the commit editor

In this case it happens across all versions ``` { "architecture": "win32-x64", "cliVersion": "@salesforce/cli/2.59.6", "nodeVersion": "node-v20.17.0", "osVersion": "Windows_NT 10.0.19045", "rootPath": "C:\\Users\\Usuario\\AppData\\Local\\sf\\client\\2.59.6-767cea4", "shell": "C:\\Program Files\\Git\\usr\\bin\\bash.exe", "pluginVersions": [ "@oclif/plugin-autocomplete 3.2.3 (core)", "@oclif/plugin-commands...

This started happening after installing the Agentforce DX plugin and tried to create an Agent. Not sure if it was a coincidence. I created a new scratch and works fine...

@fehays There is a new "alias" If you run `sf project retrieve start -m Agent` it should retrieve anything related to the agent, including topics and actions

I just updated to the most recent sf cli version and still get the same result ```json { "architecture": "darwin-arm64", "cliVersion": "@salesforce/cli/2.91.6", "nodeVersion": "node-v22.12.0", "osVersion": "Darwin 24.5.0", "rootPath": "/usr/local/lib/node_modules/@salesforce/cli", "shell":...

Also if I create a test run with this bad yaml and deploy, the test get stuck in progress for ever

That’s just the metadata retrieved from the org after uploading the csv for the testsEnviado desde mi iPhoneEl 9 jun. 2025, a la(s) 11:14 a. m., Willie Ruemmele ***@***.***> escribió:WillieRuemmele...