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
This commit is contained in:
Etan Kissling 2022-08-25 23:14:40 +02:00 committed by GitHub
parent d619b539f3
commit ebfb624557
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions

2
vendor/news vendored

@ -1 +1 @@
Subproject commit 9094ae314754908838979fe0840b9b33c0e0a603
Subproject commit 34272dedcd2586ba5b374a87c1f6d1adc6835049