RepoJournal
Meta Meta
114 wires and counting
$ status: archived — this briefing has stopped; the archive stays readable. browse live briefings →

$ status

wire 2026-05-28
stories 14
RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

REACT FIXES FLIGHT SERVER DATA LOSS UNDER BACKPRESSURE

By RepoJournal · Filed · About Meta · Composed from the cited sources · methodology

React's Flight Server was silently dropping streamed content when network backpressure hit between header and payload chunks, leaving data stranded in the queue.

The Flight Server emits Text and TypedArray rows as two separate chunks: a header containing metadata, then the content itself. When destination backpressure occurred between them, the flush would write the header and break before reaching content, leaving chunks orphaned [1]. This is the kind of silent data loss that surfaces weeks later in production. React also hardened Promise instrumentation error handling [2], throwing a recoverable error instead of undefined when rejection reasons are misconfigured in userspace. That makes debugging malformed Promises dramatically easier. On the React Native side, the team finished rolling out the iOS main queue coordinator and killed the feature flag [4], inlining the previously-gated paths into core execution. They're also cleaning up legacy infrastructure: removing unused SurfaceRegistry references [5] and applying Flow variance transforms across xplatjs [6]. The codegen script error logging got fixed [7], so build failures now actually surface instead of silencing themselves. CI infrastructure tightened up too [3], running on backport branches instead of tags to align with release protection rules.

Action items

References

  1. [1] [Flight] Fix stranded row content under Node stream backpressure ↗ facebook/react
  2. [2] Throw special error if rejected Promises are incorrectly instrumented ↗ facebook/react
  3. [3] [ci] Allow CI on backport branches ↗ facebook/react
  4. [4] Remove enableMainQueueCoordinatorOnIOS, make coordinator always-on (#56935) ↗ facebook/react-native
  5. [5] Remove legacy SurfaceRegistry reference (#56972) ↗ facebook/react-native
  6. [6] Transform readonly in xplatjs (#56973) ↗ facebook/react-native
  7. [7] Fix codegen script phase error logging (#56956) ↗ facebook/react-native

$ ls meta/reviews/ # the step-back reads

the week in review React 19.3 ships View Transitions, RN 0.88-rc breaks Touchable the month in review React, React Native, and Jest harden the stack
Full archive → Weekly reviews →

Quick answers

What shipped in Meta on May 28, 2026?
React's Flight Server was silently dropping streamed content when network backpressure hit between header and payload chunks, leaving data stranded in the queue. In total, 11 commits and 3 pull requests landed.
What were the notable Meta updates?
[Flight] Fix stranded row content under Node stream backpressure, Throw special error if rejected Promises are incorrectly instrumented, and [ci] Allow CI on backport branches.
♥

$ log Meta --recent

React Native strips dead config, React compiler fixes exponent folding 21 shipped React Native's generated SwiftPM manifests inherit the app's iOS floor, and SectionList scrolls to the right row 30 shipped React stops emulating bubbling for toggle events, fixes Fragment compareDocumentPosition 9 shipped React Native's Babel preset stops dropping Platform.select side effects 6 shipped

$ log --all # elsewhere on the wire

Alignment & Post-training GSM8K scoring parses answers as exact decimals AI Red Teaming PyRIT closes a judge-spoofing hole, promptfoo accepts Langfuse v6

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.