Fix P2P Networking call metadata#269
Merged
Merged
Conversation
✅ Deploy Preview for eth-forkcast ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
7358903 to
435ab9c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

What changed
/calls/p2p/040to the canonical/calls/p2p/001generated manifest entry.Root cause
ACDbot emitted a bad P2P artifact directory for May 20, 2026 as
2026-05-20_040, with PQ Interop-derived assets but P2P issue/video metadata. Forkcast imported that row because it had transcript/TLDR assets, while the correct2026-05-20_001row was chat-only. The root-cause fix is in ethereum/pm#2068.Validation
npm testnpm run build