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

Easier troubleshooting of failing package installation #160

Closed
krystian-panek-vmltech opened this issue Aug 10, 2023 · 2 comments · Fixed by #177
Closed

Easier troubleshooting of failing package installation #160

krystian-panek-vmltech opened this issue Aug 10, 2023 · 2 comments · Fixed by #177
Labels
improvement Improvement to an existing feature

Comments

@krystian-panek-vmltech
Copy link
Contributor

right now due to performance reasons, the package installation output is not being processed/captured fully.

when installing a package via the CRX package manager then a lot of HTML output is produced. AEMC is not buffering it as it is speeding up seriously installation time via CLI.

however, when e.g. some package installation hook fails there is no way to troubleshoot such a case. it is needed then to enter the CRX package manager and click once again "Reinstall" on the package to see the errors. maybe instead AEMC could give an option to print the installation output somehow or buffer it to file or sth that will allow easy troubleshooting.

@krystian-panek-vmltech krystian-panek-vmltech added the improvement Improvement to an existing feature label Aug 10, 2023
@krystian-panek-vmltech
Copy link
Contributor Author

AEMC is using an install service JSON endpoint, not an HTML endpoint like in GAP. when package installation fails (like hook class is unavailable), a valid message is bubbled up. to have more info about the error, it is still necessary to enter crx/packmgr manually.

I am not sure If it is worth it to hit HTML endpoint to get that package installation output.

@krystian-panek-vmltech
Copy link
Contributor Author

krystian-panek-vmltech commented Aug 24, 2023

fixed by #177

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improvement to an existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant