-
Notifications
You must be signed in to change notification settings - Fork 224
Add failsafe and improve logging on unexpected select app error #6815
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.
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
base: main
Are you sure you want to change the base?
Add failsafe and improve logging on unexpected select app error #6815
Conversation
Coverage report
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run success3715 tests passing in 1438 suites. Report generated by 🧪jest coverage report action from e86c51c |
ea40cf9 to
5d0894d
Compare
|
We detected some changes at Caution DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release. |
1d3d3b1 to
75f75ba
Compare
75f75ba to
e86c51c
Compare
| 'Try running the command again. If the issue persists:', | ||
| ' • Check system resources and stability', | ||
| ' • Try running outside of containers/WSL if applicable', | ||
| ' • Report this issue with the error detailsmad a verbose log', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| ' • Report this issue with the error detailsmad a verbose log', | |
| ' • Report this issue with the error details and a verbose log', |
| `Available apps: ${apps.length}`, | ||
| ].join('\n') | ||
|
|
||
| const tryMessage = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you extract this to avoid repetition?
| } else { | ||
| const tryMessage = [ | ||
| 'This may happen if:', | ||
| ' • The process received a signal (SIGINT, SIGTERM) or was terminated', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you press CTRL-C, the command should stop immediately. We shouldn't retry anything in that case.
But I'm not able to reproduce that behavior, is that happening?

WHY are these changes introduced?
Issue #771
vault error
Fixes an issue where app selection prompts could fail silently without proper error handling or diagnostics, leading to a poor developer experience when the prompt is interrupted.
WHAT is this pull request doing?
Adds robust error handling and retry logic to the app selection process:
How to test your changes?
shopify app devin a project with multiple appsMeasuring impact
How do we know this change was effective? Please choose one:
Checklist