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.

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

issue missing root cause of error #845 solution #933

Conversation

gauravsaini04
Copy link
Contributor

Ref: #845

Description

  • As a correction to earlier raised pr Poetry error message #852
  • As a solution to the above issue, pr achieves printing of the correct error message in the above scenario

changelog

  • Added changes to the src/spec-common/injectHeadless.ts file as well as a launch.json configuration for cli debugging at src/test/configs/poetry-example/.devcontainer.json

checklist

  • Checked that applied changes work as expected

@gauravsaini04 gauravsaini04 requested a review from a team as a code owner November 18, 2024 12:11
@chrmarti
Copy link
Contributor

@gauravsaini04 It looks like you started from a different change than the very latest in #852. Please make sure to pull in the latest from there and address my latest comment on top. Thanks!

if (name) {
infoOutput.raw(`\x1b[1mRunning ${name} of ${lifecycleHookName} from ${userCommandOrigin}...\x1b[0m\r\n${cmdOutput}\r\n`);
}
} catch (err) {
Copy link
Contributor Author

@gauravsaini04 gauravsaini04 Nov 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so basically what i understood is that you'd like me to push this code of catching the error inside runSingleCommand method to be after https://github.com/devcontainers/cli/blob/main/src/spec-common/injectHeadless.ts#L531 i.e. await Promise.all(commands), in the catch block that's written after it
( in your comment here )

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we are very close in #852. I suggest we continue there since that has all the history of the discussion. I have pushed the suggested fixes there, please take a look and leave a review. Thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

closing this as #852 was already merged.

@gauravsaini04 gauravsaini04 deleted the cli_issue_#845_missing_root_cause branch November 22, 2024 02:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants