Re: [go-nuts] rpc.debugLog unexported

Hi, I had tried a similar approach for customizing golokia . Why do we need to move the imported packages code to the project directory? Doesn't go compile using the local copy of the imported package in GOPATH? What am I missing here? 8 Aralık 2019 Pazar

Re: [go-nuts] rpc.debugLog unexported

On Sun, Dec 8, 2019 at 10:07 AM wrote: > > Thanks for your reply. Do you regularly edit standard libs as described (and > then presumably edit them back)? While debugging the standard library, yes, I do. But I also agree that for this case it might be useful to have a more usable mechanism. >

Re: [go-nuts] rpc.debugLog unexported

Thanks for your reply. Do you regularly edit standard libs as described (and then presumably edit them back)? I copied /usr/lib/go-1.13/net/rpc to my project directory, then changed all imports of "net/rpc" to "./net/rpc", and then set debugLog (in my shadow copy, not /usr/lib/go-1.13). It got t

Re: [go-nuts] rpc.debugLog unexported

On Sat, Dec 7, 2019 at 9:12 AM wrote: > > How can I turn on debugging in net/rpc/server.go? > > There is a promising variable called `debugLog` in there. How should I > toggle it? I don't know how much it will help, but the way to toggle it is to literally edit net/rpc/debug.go to set debugLog

[go-nuts] rpc.debugLog unexported

How can I turn on debugging in net/rpc/server.go? There is a promising variable called `debugLog` in there. How should I toggle it? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from i