From ebfb624557579495224af7562d475038bed3c807 Mon Sep 17 00:00:00 2001 From: Etan Kissling Date: Thu, 25 Aug 2022 23:14:40 +0200 Subject: [PATCH] bump `news` to fix concurrency bug with >1MB frames (#4028) When calling `newPayload` on a >1MB payload (can happen post-merge), `news` splits up that payload into 1MB chunks. The chunks are each sent individually, though, with `await` in-between. This means that when we send concurrent `forkChoiceUpdated` calls, that those may end up getting in-between the `newPayload` chunks, leading to invalid data being sent. The EL then returns an error message with a `null` `id` entry (as it could not read the request `id` due to the mangling) and disconnects. A PR has been submitted to fix this in `news`, and merged into `status` branch early as this fix is critical for reliable post-merge operation: https://github.com/Tormund/news/pull/22 --- vendor/news | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vendor/news b/vendor/news index 9094ae314..34272dedc 160000 --- a/vendor/news +++ b/vendor/news @@ -1 +1 @@ -Subproject commit 9094ae314754908838979fe0840b9b33c0e0a603 +Subproject commit 34272dedcd2586ba5b374a87c1f6d1adc6835049