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

More feedback from commands #51

Open
sc0ttkclark opened this issue Oct 23, 2020 · 3 comments
Open

More feedback from commands #51

sc0ttkclark opened this issue Oct 23, 2020 · 3 comments

Comments

@sc0ttkclark
Copy link
Contributor

When you run something like tric composer install or tric npm install (or other commands), it would be helpful to know after the setup is done and it's actually moved into running the command as intended. Could we add one more log line that says "Running requested command" or something like that?

It's just really hard for me to know whether some slow downs I'm experiencing is a slow down with Docker/containers/setup, or if it's the command itself.

@sc0ttkclark
Copy link
Contributor Author

I turned on tric debug and that helped a bit more

@cliffordp
Copy link
Contributor

image

@sc0ttkclark
Copy link
Contributor Author

The issue Cliff posted about is resolved (it outputs that info now), but the original request still stands -- to know at what point the command (and which command) itself is running.

For example, I'd expect to see something that tells me that it's running composer .... when calling:

slic composer validate --strict --version --no-interaction --verbose

This would be very helpful for debugging purposes as well as great detail in GitHub actions for logging purposes.

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

No branches or pull requests

2 participants