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.

Sign up for GitHub

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

Jump to bottom

Identify error sources when possible #211

Open
AaronFeledy opened this issue Sep 18, 2024 · 0 comments
Open

Identify error sources when possible #211

AaronFeledy opened this issue Sep 18, 2024 · 0 comments

Comments

@AaronFeledy
Copy link
Member

AaronFeledy commented Sep 18, 2024 •
edited
Loading

If an error originates from a dependency, we should identify it when possible. For example, when we know we are interacting with Docker and Docker throws an error, we should have some text like: Lando attempted to interact with Docker but it responded with the following error: 'I hate you.' This way I know that it's docker that hates me, not Lando.
pirog added a commit that referenced this issue Oct 10, 2024
@pirog
Rework LISTR2 support (#211)
21ab463 
* update listr2 and add a processTasks option to CLI

* remove checksToListr and push up processTasks

* add a place on the CLI to collect listr tasks

* rework listr task running

* rework listr task running part 2

* Bump to dockerfile-build branch of @lando/core for testing purposes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AaronFeledy