[go-nuts] Re: context cancellation in exec.CommandContext and os.Exit

On Sunday, January 19, 2020 at 11:45:34 PM UTC+1, Tamás Gulácsi wrote: > > Yes. > > Never call os.Exit when you still has work to be done. > Even defers are skipped. > I know. os.Exit is called in a signal handler. Thanks Manlio Perillo -- You received this message because you are

[go-nuts] Re: Advise on working with local modules

On Sunday, January 19, 2020 at 11:47:30 PM UTC+1, Tamás Gulácsi wrote: > > Why not just the replace directive in go.mod? With the replace directive to a local module, the version is ignored and the go tool always use the latest commit. Manlio Perillo -- You received this message because

[go-nuts] Re: godoc.org - Internal server error

Thanks for reporting. There's a GitHub issue tracking this, see https://github.com/golang/go/issues/36642#issuecomment-576044533. On Sunday, January 19, 2020 at 12:47:33 PM UTC-5, Steven Hartland wrote: > > Looks like somethings wrong with godoc.org atm, not sure who maintains > this as every

[go-nuts] Advise on working with local modules

Why not just the replace directive in go.mod? -- 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 it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion

[go-nuts] context cancellation in exec.CommandContext and os.Exit

Yes. Never call os.Exit when you still has work to be done. Even defers are skipped. -- 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 it, send an email to

Re: [go-nuts] Best way to buffer upstream responses in reverse proxy

Just put the missing [,] chars wher it's required with buf.WriteByte. -- 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 it, send an email to golang-nuts+unsubscr...@googlegroups.com.

[go-nuts] Advise on working with local modules

I have several personal projects in Go, and some of these projects depends on other personal projects. Since they are still in development, they are not available on a public repository. I have found a solution that seems to work, but I would like some advise. My projects are all in GOPATH

[go-nuts] godoc.org - Internal server error

Looks like somethings wrong with godoc.org atm, not sure who maintains this as every page just errors for me ATM, hence reaching out here in the hope someone who does reads this list. An example is accessing: https://godoc.org/github.com/spf13/pflag Internal server error. -- You received this

[go-nuts] Re: Uncanny behaviour while syscalls

As a first step, try printing out the error returned by syscall.Chroot() -- 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 it, send an email to

[go-nuts] context cancellation in exec.CommandContext and os.Exit

Hi. Suppose I have a program that spawns a process with exec.CommandContex and, in a signal handler, cancel the context and calls os.Exit(1). Is it possible, in theory, that the program exits before the process is actually terminated? Thanks Manlio Perillo -- You received this message

[go-nuts] Uncanny behaviour while syscalls

I'm trying to write a container daemon in GoLang. For some reason, I'm getting stuck on sycall.Chroot(), that one line alone is not working due to some reasons and I can't seem to figure it out. Any help will be appreciated. Thank you! -- You received this message because you are subscribed

Re: [go-nuts] go under rtems on arm?

thanks Ian, i hadn't realised that rtems is really a “single main that runs forever” class of rtos - i thought it was more akin to qnx. go is not going to work natively on this product range, though we will run it on a separate vm, and already run a similar app under linux on other products.

Re: [go-nuts] Best way to buffer upstream responses in reverse proxy

Hello, I am able to buffer in types.Buffer the multiple response before writing back to client, I am hit at a problem of JSON formatting the final output. Example: after first response buf = {...}, after second buf={...}{...}. Now it will be returned as is, which is not in proper json format.