Ctrl-c to exit running process throws ExitError: EEXIT: 130
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- node.js, typescript
Research direction
Reproduce the issue with sf lightning dev app --target-org and Ctrl-C, then inspect the LightningDevApp.exit path shown through @oclif/core/lib/errors/exit.js and @salesforce/sf-plugins-core/lib/sfCommand.js. Done means the running plugin and Node process stop gracefully without exposing an ExitError: EEXIT: 130 stack trace.
Written by the indexing model from the issue text.
Description
Summary
The plugin opens and runs properly, but when trying to simply kill the running process in terminal with Ctrl-c, the process does not exit gracefully, throws ExitError: EEXIT: 130
Also the local url is still available in the tab to navigate (not sure if this should be intended) but changes are not reflected when making them locally (intended)
Steps To Reproduce:
- Run the plugin with
sf lightning dev app --target-org - Exit program in same running terminal window with Ctrl-c
Expected Result
A message or something stating the plugin and node process has stopped running
Actual Result
Waiting to resolve the Lightning Experience-enabled custom domain...... done
^C/Users/tjodwalis/.local/share/sf/node_modules/@salesforce/plugin-lightning-dev/node_modules/@oclif/core/lib/errors/exit.js:6
throw new exit_1.ExitError(code);
^
ExitError: EEXIT: 130
at Object.exit (/Users/tjodwalis/.local/share/sf/node_modules/@salesforce/plugin-lightning-dev/node_modules/@oclif/core/lib/errors/exit.js:6:11)
at LightningDevApp.exit (/Users/tjodwalis/.local/share/sf/node_modules/@salesforce/plugin-lightning-dev/node_modules/@oclif/core/lib/command.js:183:16)
at process.<anonymous> (file:///Users/tjodwalis/.local/share/sf/node_modules/@salesforce/plugin-lightning-dev/node_modules/@salesforce/sf-plugins-core/lib/sfCommand.js:265:22)
at process.emit (node:events:531:35)
at Signal.callbackTrampoline (node:internal/async_hooks:130:17) {
code: 'EEXIT',
oclif: { exit: 130 },
skipOclifErrorHandling: undefined,
suggestions: undefined
}
Node.js v21.4.0
Additional Information
Screenshots:
Please see actual result above ^^
Logs:
Please see actual result above ^^
System Information
SF CLI:
zsh
{
"architecture": "darwin-arm64",
"cliVersion": "@salesforce/cli/2.68.6",
"nodeVersion": "node-v21.4.0",
"osVersion": "Darwin 23.6.0",
"rootPath": "/Users/tjodwalis/.nvm/versions/node/v21.4.0/lib/node_modules/@salesforce/cli",
"shell": "zsh",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.2.10 (core)",
"@oclif/plugin-commands 4.1.10 (core)",
"@oclif/plugin-help 6.2.18 (core)",
"@oclif/plugin-not-found 3.2.28 (core)",
"@oclif/plugin-plugins 5.4.17 (core)",
"@oclif/plugin-search 1.2.16 (core)",
"@oclif/plugin-update 4.6.13 (core)",
"@oclif/plugin-version 2.2.16 (core)",
"@oclif/plugin-warn-if-update-available 3.1.23 (core)",
"@oclif/plugin-which 3.2.19 (core)",
"@salesforce/cli 2.68.6 (core)",
"apex 3.6.3 (core)",
"api 1.3.2 (core)",
"auth 3.6.75 (core)",
"data 3.11.4 (core)",
"deploy-retrieve 3.15.13 (core)",
"info 3.4.21 (core)",
"lightning-dev 1.9.4 (user) published 10 days ago (Mon Nov 25 2024)",
"limits 3.3.40 (core)",
"marketplace 1.3.6 (core)",
"org 5.2.4 (core)",
"packaging 2.9.3 (core)",
"schema 3.3.42 (core)",
"settings 2.4.6 (core)",
"sobject 1.4.46 (core)",
"telemetry 3.6.23 (core)",
"templates 56.3.30 (core)",
"trust 3.7.43 (core)",
"user 3.6.3 (core)",
"@salesforce/sfdx-scanner 4.6.0 (user) published 72 days ago (Tue Sep 24 2024) (latest is 4.7.0)"
]
}
OS:
Apple M3 Pro 14.7.1 (23H222)
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 19
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from salesforcecli/plugin-lightning-dev
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
salesforcecli/plugin-lightning-dev#686 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
salesforcecli/plugin-lightning-dev#627 · 2 comments · 1 reaction ·
-
BUG P2
Difficulty 3/5 1-2 days Newbie friendliness 45/100
salesforcecli/plugin-lightning-dev#544 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
salesforcecli/plugin-lightning-dev#456 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in salesforcecli/plugin-lightning-dev
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/inspector#2458 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
railmapgen/rmp-gallery#4068 ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
carbon-design-system/ibm-products#9907 ·