-
Notifications
You must be signed in to change notification settings - Fork 74
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
Segfault when Scheme not defined #1050
Comments
Ok, according to the go docs:
If the code in the go client is modified to the following, a missing schema is not causing a segfault anymore. // was: if len(url.Scheme) == 0 || len(url.Host) == 0 {
if url==nil || len(url.Scheme) == 0 || len(url.Host) == 0 {
urlBase = fmt.Sprintf("https://%s/api", host)
url, err = url.Parse(urlBase)
} Does this has to be fixed or must the user set the scheme in the first place? |
The user should not be required to set the scheme. Sorry this issue got overlooked for two months. |
Update client-go to latest; Fixes apache#1050.
Update client-go to latest; Fixes #1050.
Wskdeploy crashes with a Segfault when the URL Scheme is not defined in
apihost
:To reproduce the segfault:
in contrast, the following works:
The segfault seems to originate this code
the error:
Do we have to set the scheme in the apihost or should the code in
GetUrlBase
handle this correctly?The text was updated successfully, but these errors were encountered: