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
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