You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 22, 2020. It is now read-only.
I am not sure whether it is a bug of torus or golang itself. I file a bug here for deep discussion. my case
when I run the cmd "torusctl init" with the newest go version, I got the following error message:
start to init MDS...
MDS init finished...
invalid etcd address: parse 127.0.0.1:2379: first path segment in URL cannot contain colon root cause
I found the golang community changed its url.Parse method after I research into the code. they think "127.0.0.1:2379" is no longer the correct address according to RFC 3986. it raises the error message from the "flagconfig.BuildConfigFromFlags" when parse the "defaultEtcdAddress" via url.Parse
The text was updated successfully, but these errors were encountered:
freesky-edward
changed the title
The default etcd address can't be parsed correctly on the newest go version
The default etcd address can't be parsed correctly on the latest golang version
Jan 11, 2017
I am not sure whether it is a bug of torus or golang itself. I file a bug here for deep discussion.
my case
when I run the cmd "torusctl init" with the newest go version, I got the following error message:
start to init MDS...
MDS init finished...
invalid etcd address: parse 127.0.0.1:2379: first path segment in URL cannot contain colon
root cause
I found the golang community changed its url.Parse method after I research into the code. they think "127.0.0.1:2379" is no longer the correct address according to RFC 3986. it raises the error message from the "flagconfig.BuildConfigFromFlags" when parse the "defaultEtcdAddress" via url.Parse
The text was updated successfully, but these errors were encountered: