Thanks for your help on this, Michael.
Yes, the fix seems pretty simple and porting to older Go releases will
ensure people are not getting those super awkward messages randomly.
I have created a Trello card with a checklist so we can track all the
distributions that we need to fix, and included
Thank you Alfonso for that link (I didn't find that when I looked, so
kudos), and thank you Michael and Zyga for all your work on this!
On 12 March 2017 at 08:38, Michael Hudson-Doyle
wrote:
> PS: I guess I should back port that Go fix to all supported Go releases?
that would be very nice. Does
PS: I guess I should back port that Go fix to all supported Go releases?
On 12 March 2017 at 21:37, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
> Before we get into this, what is the actual problem here? Just the ugly
> messages?
>
> On 11 March 2017 at 02:58, Alfonso Sanchez-Beat
Before we get into this, what is the actual problem here? Just the ugly
messages?
On 11 March 2017 at 02:58, Alfonso Sanchez-Beato <
alfonso.sanchez-be...@canonical.com> wrote:
> On Fri, Mar 10, 2017 at 10:22 AM, John Lenton
> wrote:
>
> > Hello!
> >
> > We're seeing a weird issue with either go
On Fri, Mar 10, 2017 at 10:22 AM, John Lenton
wrote:
> Hello!
>
> We're seeing a weird issue with either go, pthreads, or the kernel. If
> you're knowledgeable about one or more of those things, could you take
> a look? Thank you.
>
> The issue manifests as nasty warnings from the "snap run" comm
On Fri, 10 Mar 2017 09:22:45 +, John Lenton wrote:
> Hello!
>
> We're seeing a weird issue with either go, pthreads, or the kernel. If
> you're knowledgeable about one or more of those things, could you take
> a look? Thank you.
>
> The issue manifests as nasty warnings from the "snap run" comm
