-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Improve the communication for automatic extension resolution #5082
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: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
@@ -89,7 +89,7 @@ func (l *launcher) launch(cmd *cobra.Command, args []string) error { | |||||||||
if err != nil { | ||||||||||
l.gs.Logger. | ||||||||||
WithError(err). | ||||||||||
Error("Automatic extension resolution is enabled but it failed to analyze the dependencies." + | ||||||||||
Error("Failed to analyze the extensions required." + | ||||||||||
" Please, make sure to report this issue by opening a bug report.") | ||||||||||
return err | ||||||||||
} | ||||||||||
|
@@ -103,8 +103,8 @@ func (l *launcher) launch(cmd *cobra.Command, args []string) error { | |||||||||
|
||||||||||
l.gs.Logger. | ||||||||||
WithField("deps", deps). | ||||||||||
Info("Automatic extension resolution is enabled. The current k6 binary doesn't satisfy all dependencies," + | ||||||||||
" it's required to provision a custom binary.") | ||||||||||
Info("Provisioning a custom binary as the current doesn't satisfy all dependencies," + | ||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit;
Suggested change
I think it's slightly more precise and clear There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Overall, I'm wondering whether we should use either There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Some thoughts:
I have made proposal below There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I guess after the discussion now nad looking more closely at some of the code:
I do reall think it will be nice to one differntiate between those two case and potentially list both the binary link and potentially the binary path on the fs. Maybe not at Info but debug level There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I guess the word I will look deeper into a better proposal. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
@mstoykov same for provisioning. I guess it used to collect the two operations (build + download). |
||||||||||
" may take a few seconds as it needs to download the new one.") | ||||||||||
Comment on lines
+106
to
+107
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
The current listing of |
||||||||||
|
||||||||||
customBinary, err := l.provisioner.provision(deps) | ||||||||||
if err != nil { | ||||||||||
|
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.