Message-ID length limit !

Message-ID length limit !

[Neil Armstrong]

Hi,

It seems I'm hitting a message-id length limit when sending with b4, here's a 2 patches thread:

0/2 https://lore.kernel.org/all/20230110-topic-sm8550-upstream-display-defconfig-v2-0-c29b9714c85f@linaro.org/
1/2 https://lore.kernel.org/all/20230110-topic-sm8550-upstream-display-defconfig-v2-1-c29b9714c85f@linaro.org/
2/2 https://lore.kernel.org/all/20230110-topic-sm8550-upstream-display-defconfig-v2-2-c29b9714c85f@linaro.org/

Neither lore or thunderbird shows the thread correctly, so it seems the message-id is too long, right ?

And trying to apply the thread with b4 fails :
$ b4 am 20230110-topic-sm8550-upstream-display-defconfig-v2-0-c29b9714c85f@linaro.org
Grabbing thread from lore.kernel.org/all/20230110-topic-sm8550-upstream-display-defconfig-v2-0-c29b9714c85f%40linaro.org/t.mbox.gz
Analyzing 1 messages in the thread
No patches found.

$ b4 am 20230110-topic-sm8550-upstream-display-defconfig-v2-1-c29b9714c85f@linaro.org
Grabbing thread from lore.kernel.org/all/20230110-topic-sm8550-upstream-display-defconfig-v2-1-c29b9714c85f%40linaro.org/t.mbox.gz
Analyzing 1 messages in the thread
Checking attestation on all messages, may take a moment...
---
   ✓ [PATCH v2 1/2] arm64: defconfig: enable SM8550 DISPCC clock driver
     ✓ Signed: DKIM/linaro.org
   ERROR: missing [2/2]!
---
Total patches: 1
---
WARNING: Thread incomplete!
  Link: https://lore.kernel.org/r/20230110-topic-sm8550-upstream-display-defconfig-v2-1-c29b9714c85f@linaro.org
  Base: not specified
        git am ./v2_20230112_neil_armstrong_arm64_defconfig_enable_sm8550_dispcc_clock_driver.mbx


$ b4 am 20230110-topic-sm8550-upstream-display-defconfig-v2-2-c29b9714c85f@linaro.org
Grabbing thread from lore.kernel.org/all/20230110-topic-sm8550-upstream-display-defconfig-v2-2-c29b9714c85f%40linaro.org/t.mbox.gz
Analyzing 1 messages in the thread
Checking attestation on all messages, may take a moment...
---
   ERROR: missing [1/2]!
   ✓ [PATCH v2 2/2] arm64: defconfig: enable Visionox VTDR6130 DSI Panel driver
     ✓ Signed: DKIM/linaro.org
---
Total patches: 1
---
WARNING: Thread incomplete!
  Link: https://lore.kernel.org/r/20230110-topic-sm8550-upstream-display-defconfig-v2-2-c29b9714c85f@linaro.org
  Base: not specified
        git am ./v2_20230112_neil_armstrong_arm64_defconfig_enable_visionox_vtdr6130_dsi_panel_driver.mbx


I'm running:
$ b4 --version
0.11.1

Thanks,
Neil

-- 
Neil Armstrong <neil.armstrong@linaro.org>
Senior Software Engineer - Linaro Developer Services
https://linaro.org/services

Re: Message-ID length limit !

[Konstantin Ryabitsev]

On Thu, Jan 12, 2023 at 10:53:56AM +0100, Neil Armstrong wrote:
> 
> Hi,
> 
> It seems I'm hitting a message-id length limit when sending with b4, here's a 2 patches thread:
> 
> 0/2 https://lore.kernel.org/all/20230110-topic-sm8550-upstream-display-defconfig-v2-0-c29b9714c85f@linaro.org/
> 1/2 https://lore.kernel.org/all/20230110-topic-sm8550-upstream-display-defconfig-v2-1-c29b9714c85f@linaro.org/
> 2/2 https://lore.kernel.org/all/20230110-topic-sm8550-upstream-display-defconfig-v2-2-c29b9714c85f@linaro.org/
> 
> Neither lore or thunderbird shows the thread correctly, so it seems the message-id is too long, right ?

Oh, look, you found yet another bug in Python's email module. This brings the
critical bugs count to 4. For no reason at all, it decided to qp-encode the
References and In-Reply-To headers:

	Message-Id: <20230110-topic-sm8550-upstream-display-defconfig-v2-1-c29b9714c85f@linaro.org>
	References: =?utf-8?q?=3C20230110-topic-sm8550-upstream-display-defconfig-v2?=
	 =?utf-8?q?-0-c29b9714c85f=40linaro=2Eorg=3E?=
    In-Reply-To: =?utf-8?q?=3C20230110-topic-sm8550-upstream-display-defconfig-v?=
     =?utf-8?q?2-0-c29b9714c85f=40linaro=2Eorg=3E?=

I've reported this as https://github.com/python/cpython/issues/100991

I can't express how frustrating this is, but at least the work I've done this
week on completely avoiding Python's email generation modules will help.

I will probably end up releasing 0.12 sooner than later, seeing as everyone's
work is impacted by the quality of Python's email routines.

-K

Re: Message-ID length limit !

[Neil Armstrong]

On 12/01/2023 16:26, Konstantin Ryabitsev wrote:
> On Thu, Jan 12, 2023 at 10:53:56AM +0100, Neil Armstrong wrote:
>>
>> Hi,
>>
>> It seems I'm hitting a message-id length limit when sending with b4, here's a 2 patches thread:
>>
>> 0/2 https://lore.kernel.org/all/20230110-topic-sm8550-upstream-display-defconfig-v2-0-c29b9714c85f@linaro.org/
>> 1/2 https://lore.kernel.org/all/20230110-topic-sm8550-upstream-display-defconfig-v2-1-c29b9714c85f@linaro.org/
>> 2/2 https://lore.kernel.org/all/20230110-topic-sm8550-upstream-display-defconfig-v2-2-c29b9714c85f@linaro.org/
>>
>> Neither lore or thunderbird shows the thread correctly, so it seems the message-id is too long, right ?
> 
> Oh, look, you found yet another bug in Python's email module. This brings the
> critical bugs count to 4. For no reason at all, it decided to qp-encode the
> References and In-Reply-To headers:
> 
> 	Message-Id: <20230110-topic-sm8550-upstream-display-defconfig-v2-1-c29b9714c85f@linaro.org>
> 	References: =?utf-8?q?=3C20230110-topic-sm8550-upstream-display-defconfig-v2?=
> 	 =?utf-8?q?-0-c29b9714c85f=40linaro=2Eorg=3E?=
>      In-Reply-To: =?utf-8?q?=3C20230110-topic-sm8550-upstream-display-defconfig-v?=
>       =?utf-8?q?2-0-c29b9714c85f=40linaro=2Eorg=3E?=
> 
> I've reported this as https://github.com/python/cpython/issues/100991

Interesting...

> 
> I can't express how frustrating this is, but at least the work I've done this
> week on completely avoiding Python's email generation modules will help.
> 
> I will probably end up releasing 0.12 sooner than later, seeing as everyone's
> work is impacted by the quality of Python's email routines.

Thanks :-)

> 
> -K