having an expired scratch org as the default target-org causes the CLI to hang trying to connect to it #3015
Labels
bug
Issue or pull request that identifies or fixes a bug
doctor
Issue was created using the 'doctor' command
investigating
We're actively investigating this issue
validated
Version information for this issue has been validated
If I create a scratch org, set it as the default with
sf config set target-org <org-username> --global
then left it expire,sf
still tries to connect to it and causes a ~10s delay on all commands executions (it tries to conect to the instance URL, which isn't valid at that point.Expected result
if the target-org expired then it should be ignored
Actual result
expired target-org causes a ~10s delay on all commands (even if it's not using
--target-org
likesf plugins
).Additional information
Internal:
here's a video of the bug running
JSFORCE_LOG_LEVEL=DEBUG sf config list --dev-debug
, see how it hangs on retrying the request:https://salesforce-internal.slack.com/archives/G02K6C90RBJ/p1725468814588979
System Information
Diagnostics
✅ pass - salesforcedx plugin isn’t installed
✅ pass - you don't have any linked plugins
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.yarnpkg.com
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org/
✅ pass - using latest or latest-rc CLI version
❌ warn - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches apiVersion
✅ pass - can access: https://test.salesforce.com
✅ pass - can access: https://appexchange.salesforce.com/services/data
✅ pass - can access: https://developer.salesforce.com/media/salesforce-cli/sf/channels/stable/sf-win32-x64-buildmanifest
✅ pass - [@salesforce/plugin-auth] CLI supports v2 crypto
The text was updated successfully, but these errors were encountered: