Re: [go-nuts] Re: Golang upgrade from 1.5 to 1.7.2

+1 https://github.com/samuel/go-zookeeper. already used in PRO env. 在 2016年8月24日星期三 UTC+8上午7:27:56，Matt Harden写道： > > You're right of course. I was thinking of > https://github.com/samuel/go-zookeeper. > > On Tue, Aug 23, 2016 at 4:04 PM Prateek Gaur > wrote: > >> BTW this thing worked fine in

Re: [go-nuts] Re: Golang upgrade from 1.5 to 1.7.2

You're right of course. I was thinking of https://github.com/samuel/go-zookeeper. On Tue, Aug 23, 2016 at 4:04 PM Prateek Gaur wrote: > BTW this thing worked fine in 1.5.2 version of go linker. > > > On Monday, August 22, 2016 at 12:20:38 PM UTC-7, Prateek Gaur wrote: > >> In order to use one

[go-nuts] Re: Golang upgrade from 1.5 to 1.7.2

BTW this thing worked fine in 1.5.2 version of go linker. On Monday, August 22, 2016 at 12:20:38 PM UTC-7, Prateek Gaur wrote: > > In order to use one of the go > packages I updates my golang version from 1.5.2 to 1.7. > > But after update my go binaries s

[go-nuts] Re: Golang upgrade from 1.5 to 1.7.2

Actually gozk does use cgo. Check here . gozk is a wrapper on top of c client which is a wrapper on top of java code. Not if we check the symbols present in c client of zookeeper, we'll see : 204: 0001313f 132 FUNCLOCAL DEFAULT

Re: [go-nuts] Re: Golang upgrade from 1.5 to 1.7.2

Consider using gozk , which doesn't require cgo. On Mon, Aug 22, 2016 at 4:29 PM Prateek Gaur wrote: > This is a weird interface. Looks like I can reply back only to my message. > Anyway. > > I think your analysis is spot on Ian. All the binaries w

[go-nuts] Re: Golang upgrade from 1.5 to 1.7.2

This is a weird interface. Looks like I can reply back only to my message. Anyway. I think your analysis is spot on Ian. All the binaries which depend on zookeeper are segfaulting whereas others are working fine. Zookeeper (zk.go) depends on cgo. I think our toolchain which has the built zooke