On Wednesday, April 4, 2018 at 2:59:06 PM UTC+2, Dave Cheney wrote:
>
> You can report issues with Go at this link, golang.org/issue/new.
>
> However, this looks like a docker weirdness so we cannot help you as the
> bug isn't in go, it's docker weirdness.
>
> Please try their support forums,
You can report issues with Go at this link, golang.org/issue/new.
However, this looks like a docker weirdness so we cannot help you as the
bug isn't in go, it's docker weirdness.
Please try their support forums, sorry I don't have those details, i've
never tried to get support for their
On Tuesday, April 3, 2018 at 4:50:36 PM UTC+2, Dave Cheney wrote:
>
> I’ve not seen that problem before. I’d hazard a guess that it’s an
> incorrect go installation. Don’t set goroot, basically ever. But it’s just
> a guess.
>
It is basically problem when I run in docker container. This is
I’ve not seen that problem before. I’d hazard a guess that it’s an incorrect go
installation. Don’t set goroot, basically ever. But it’s just a guess.
Are you able to create a stand alone program that demonstrates the issue with
the profile? Please consider raising a bug, golang.org/issue/new
On Saturday, March 31, 2018 at 12:15:34 AM UTC+2, Dave Cheney wrote:
>
> It looks like you’re stopping the block profile immediately after starting
> it.
>
> Try github.com/pkg/profile which will take care of the plumbing for you.
Thanks Dave for pointing your code.
After viewing your code,
