-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Binary provisioning] Exclude fallback path #4730
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
Conversation
506e47e
to
d3a17d6
Compare
internal/cmd/launcher.go
Outdated
reportIssues := "If you encounter any unexpected user experience or something doesn't go as planned," + | ||
" please report it by creating an issue." | ||
|
||
l.gs.Logger.Info("Experimental feature for Binary provisioning is enabled." + |
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.
In #4731 we removed this information message.
d3a17d6
to
3c5bb93
Compare
3c5bb93
to
504e761
Compare
internal/cmd/launcher.go
Outdated
Error("Failed to provision a k6 binary with required dependencies." + | ||
" Please, make sure to report this issue by opening a bug report.") | ||
Error("Failed to provision a k6 binary with required dependencies. " + | ||
reportIssues) |
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.
We shouldn't reuse report Issues
here as it will produce this weird message. We are reporting an error and still saying If you encounter any unexpected user experience or something didn't go as planned
ERRO[0000] Failed to provision a k6 binary with required dependencies. If you encounter any unexpected user experience or something didn't go as planned, please report it by creating an issue. error="invalid build parameters: cannot satisfy dependency : k6/x/faker >0.5.0"
reportIssues) | |
" Please, make sure to report this issue by opening a bug report.") |
internal/cmd/launcher.go
Outdated
Debug("Binary provisioning feature is enabled.") | ||
Debug("Binary Provisioning feature is enabled.") | ||
|
||
reportIssues := "If you encounter any unexpected user experience or something didn't go as planned," + |
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.
I think this message made more sense when we had the INFO
message about binary provisioning enable. Now I don't see we should use it. See my comments on the error messages.
internal/cmd/launcher.go
Outdated
Error("Binary provisioning is enabled but it failed to analyze the dependencies." + | ||
" Please, make sure to report this issue by opening a bug report.") | ||
Error("Binary Provisioning is enabled but it failed to analyze the dependencies. " + | ||
reportIssues) |
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.
Seme problem here with reusing reportIssues
reportIssues) | |
" Please, make sure to report this issue by opening a bug report.") |
What?
Changes to improve the UX.
Why?
There is also a change that skips the launcher very early in the root code. As we are still early days, it might be better if we don't take a risk disrupting the stable execution path.
Checklist
make check
) and all pass.Checklist: Documentation (only for k6 maintainers and if relevant)
Please do not merge this PR until the following items are filled out.
Related PR(s)/Issue(s)