llvm dev - Feb 2020 - MLIR changes not sent to any mailing lists?

On 02/06/2020 02:48 PM, Greg Bedwell wrote:
>     Here's a non-MLIR commit that also wasn't sent to any list:
>     b3576f60ebc8f660afad8120a72473be47517573
> 
> 
> I don't think that this is the same issue as the mlir commits.  This
particular one is likely due to the issue of non-ascii characters the commit
summary (author/comitter name in this case) causing some sort of failure
somewhere in the email pipeline, resulting in emails not turning up on the list:
> http://lists.llvm.org/pipermail/llvm-dev/2019-August/134516.html 
> http://lists.llvm.org/pipermail/llvm-dev/2019-November/137292.html 
> http://lists.llvm.org/pipermail/llvm-dev/2019-December/137508.html 
> My guess is that somewhere on some server involved in sending the emails
there's a series of error messages hiding in a logfile about invalid ascii
characters from some software that isn't utf-8 aware.  I don't know who
owns that process though.
> 
You are correct, this second email is the same non-ascii issue.  I
think we have a fix now and hopefully we'll be able to deploy it soon.

-Tom
> -Greg
>

Nice.  Thanks Tom!

On Thu, 6 Feb 2020 at 22:52, Tom Stellard <tstellar at redhat.com> wrote:
> On 02/06/2020 02:48 PM, Greg Bedwell wrote:
> >     Here's a non-MLIR commit that also wasn't sent to any
list:
> >     b3576f60ebc8f660afad8120a72473be47517573
> >
> >
> > I don't think that this is the same issue as the mlir commits. 
This
> particular one is likely due to the issue of non-ascii characters the
> commit summary (author/comitter name in this case) causing some sort of
> failure somewhere in the email pipeline, resulting in emails not turning up
> on the list:
> > http://lists.llvm.org/pipermail/llvm-dev/2019-August/134516.html
> > http://lists.llvm.org/pipermail/llvm-dev/2019-November/137292.html
> > http://lists.llvm.org/pipermail/llvm-dev/2019-December/137508.html
> > My guess is that somewhere on some server involved in sending the
emails
> there's a series of error messages hiding in a logfile about invalid
ascii
> characters from some software that isn't utf-8 aware.  I don't know
who
> owns that process though.
> >
>
> You are correct, this second email is the same non-ascii issue.  I
> think we have a fix now and hopefully we'll be able to deploy it soon.
>
> -Tom
>
> > -Greg
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200206/1b219b66/attachment.html>

On Thu, Feb 6, 2020 at 11:52 PM Tom Stellard <tstellar at redhat.com>
wrote:
>
> On 02/06/2020 02:48 PM, Greg Bedwell wrote:
> >     Here's a non-MLIR commit that also wasn't sent to any
list:
> >     b3576f60ebc8f660afad8120a72473be47517573
> >
> >
> > I don't think that this is the same issue as the mlir commits. 
This particular one is likely due to the issue of non-ascii characters the
commit summary (author/comitter name in this case) causing some sort of failure
somewhere in the email pipeline, resulting in emails not turning up on the list:
> > http://lists.llvm.org/pipermail/llvm-dev/2019-August/134516.html
> > http://lists.llvm.org/pipermail/llvm-dev/2019-November/137292.html
> > http://lists.llvm.org/pipermail/llvm-dev/2019-December/137508.html
> > My guess is that somewhere on some server involved in sending the
emails there's a series of error messages hiding in a logfile about invalid
ascii characters from some software that isn't utf-8 aware.  I don't
know who owns that process though.
> >
>
> You are correct, this second email is the same non-ascii issue.  I
> think we have a fix now and hopefully we'll be able to deploy it soon.
That's great, thanks!

On Thu, 6 Feb 2020, Tom Stellard via llvm-dev wrote:
> On 02/06/2020 02:48 PM, Greg Bedwell wrote:
>>     Here's a non-MLIR commit that also wasn't sent to any list:
>>     b3576f60ebc8f660afad8120a72473be47517573
>> 
>> 
>> I don't think that this is the same issue as the mlir commits. 
This particular one is likely due to the issue of non-ascii characters the
commit summary (author/comitter name in this case) causing some sort of failure
somewhere in the email pipeline, resulting in emails not turning up on the list:
>> http://lists.llvm.org/pipermail/llvm-dev/2019-August/134516.html 
>> http://lists.llvm.org/pipermail/llvm-dev/2019-November/137292.html 
>> http://lists.llvm.org/pipermail/llvm-dev/2019-December/137508.html 
>> My guess is that somewhere on some server involved in sending the
emails there's a series of error messages hiding in a logfile about invalid
ascii characters from some software that isn't utf-8 aware.  I don't
know who owns that process though.
>> 
>
> You are correct, this second email is the same non-ascii issue.  I
> think we have a fix now and hopefully we'll be able to deploy it soon.
Looks like this works now - now I saw the first mail for a commit from 
myself since the transition to git. Thanks!

// Martin

On 02/10/2020 01:02 PM, Martin Storsjö wrote:
> On Thu, 6 Feb 2020, Tom Stellard via llvm-dev wrote:
> 
>> On 02/06/2020 02:48 PM, Greg Bedwell wrote:
>>>     Here's a non-MLIR commit that also wasn't sent to any
list:
>>>     b3576f60ebc8f660afad8120a72473be47517573
>>>
>>>
>>> I don't think that this is the same issue as the mlir commits. 
This particular one is likely due to the issue of non-ascii characters the
commit summary (author/comitter name in this case) causing some sort of failure
somewhere in the email pipeline, resulting in emails not turning up on the list:
>>> http://lists.llvm.org/pipermail/llvm-dev/2019-August/134516.html
http://lists.llvm.org/pipermail/llvm-dev/2019-November/137292.html
http://lists.llvm.org/pipermail/llvm-dev/2019-December/137508.html My guess is
that somewhere on some server involved in sending the emails there's a
series of error messages hiding in a logfile about invalid ascii characters from
some software that isn't utf-8 aware.  I don't know who owns that
process though.
>>>
>>
>> You are correct, this second email is the same non-ascii issue.  I
>> think we have a fix now and hopefully we'll be able to deploy it
soon.
> 
> Looks like this works now - now I saw the first mail for a commit from
myself since the transition to git. Thanks!
> 
Yes, the utf-8 issue has been fixed, and there is now an mlir-commits list.

-Tom
> // Martin
>