facebook/react
Pull Requests
Succeeded
#20456
Add <Cache /> component with support for refreshing
Succeeded
#28079
Add waitForEvents to test ReactDOMEventListener
Succeeded
#18723
Modern Event System: fix fiber ancestor issue with invalid containers
Succeeded
#28883
Remove warning for ref cleanup function
Succeeded
#28881
Don't minify symbols in production builds
Succeeded
#28880
Build react-reconciler for FB builds
Succeeded
#28879
Unrevert "Support writing to this.refs from userspace"
Succeeded
#28878
[Experiment] Reuse memo cache after interruption
Succeeded
#28877
Revert "Support writing to this.refs from userspace"
Succeeded
#28875
convert circleci workflow devtools_regression_tests to github actions
Succeeded
#28874
Deprecate `renderToStaticNodeStream` (#28872)
Succeeded
#28873
Remove `renderToStaticNodeStream`
Succeeded
#28872
Deprecate `renderToStaticNodeStream`
Succeeded
#28871
[Fizz] escape <script> textContent similar to bootstrapScript
Succeeded
#28870
[Fizz] escape <style> textContent as css
Succeeded
#28869
Write Diff Train import branch to this repo
Succeeded
#28868
[Fiber/Fizz] Support AsyncIterable as Children and AsyncGenerator Client Components
Succeeded
#28867
Support writing to this.refs from userspace
Succeeded
#28865
Revert "convert circleci workflow devtools_regression_tests to github actions"
Succeeded
#28864
Remove ReactFlightFB bundles
Succeeded
#28860
Add missing bundle types for ReactCacheOld
Succeeded
#28859
delete useless eslint-disable-next-line
Succeeded
#28858
[Devtools] Rename Forget badge
Succeeded
#28857
Update ReactNativeTypes for root options (part 2)
Succeeded
#28856
Complete the typo fix
Succeeded
#28855
console test utils fix: match entire string, not just first letter
Succeeded
#28854
[Flight / Flight Reply] Encode Iterator separately from Iterable
Succeeded
#28853
Warn for Child Iterator of all types but allow Generator Components
Succeeded
#28852
Test top level fragment inside lazy semantics
Succeeded
#28851
Promote ASYNC_ITERATOR symbol to React Symbols
Succeeded
#28850
Add ReactNativeTypes for root options
Succeeded
#28849
[Flight] Support (Async) Generator ServerComponent
Succeeded
#28847
[Flight] Encode ReadableStream and AsyncIterables
Succeeded
#28846
Enable flag disableClientCache
Succeeded
#28845
Ensure sizebot doesn't swallow large diffs
Succeeded
#28844
Delete AUTHORS.md
Succeeded
#28843
Bump version from 18.2 to 18.3
Succeeded
#28842
Add early return to diffProperties
Succeeded
#28841
Create Fabric-specific version of ReactNativeAttributesPayload
Succeeded
#28840
React DevTools 5.0.2 -> 5.1.0
Succeeded
#28837
Flush direct streams in Bun
Succeeded
#28836
Add on(Caught|Uncaught|Recoverable) opts to RN
Succeeded
#28835
Fix mistaken "react-server" condition
Succeeded
#28834
Revert to use console.error for onRecoverableError on RN
Succeeded
#28833
Tests for effects behavior in modern and legacy strict modes during fast refresh
Succeeded
#28832
feat[devtools-fusebox]: support theme option
Succeeded
#28831
[Devtools] Look for a ReactMemoCacheSentinel on state
Succeeded
#28830
style: remove extra space for `package.json`
Succeeded
#28829
Remove redundant props assign
Succeeded
#28828
Remove `flight-browser` fixture
Succeeded
#28827
Run Closure on non-minified prod builds, too
Succeeded
#28826
Add failing test for string ref bug
Succeeded
#28825
Fix nightly release job for real
Build Activity
Succeeded
#84244
Fix cross-fork discrepancy I missed a few lines when syncing an earlier step. Usually I would find which one and patch it but I'm about to squash and merge so meh.
Succeeded
#84237
Fix cross-fork discrepancy I missed a few lines when syncing an earlier step. Usually I would find which one and patch it but I'm about to squash and merge so meh.
Succeeded
#84194
Detect refreshes by comparing to previous parent Removes the fresh/stale distinction from the context stack and instead detects refreshes by comparing the previous and next parent cache. This is closer to one of the earlier implementation drafts, and...
Failed
#84113
Detect refreshes by comparing to previous parent Removes the fresh/stale distinction from the context stack and instead detects refreshes by comparing the previous and next parent cache. This is closer to one of the earlier implementation drafts, and...
Succeeded
#84099
Detect refreshes by comparing to previous parent Removes the fresh/stale distinction from the context stack and instead detects refreshes by comparing the previous and next parent cache. This is closer to one of the earlier implementation drafts, and...
Succeeded
#84096
Detect refreshes by comparing to previous parent Removes the fresh/stale distinction from the context stack and instead detects refreshes by comparing the previous and next parent cache. This is closer to one of the earlier implementation drafts, and...
Succeeded
#83988
Remove provider fiber from cache context I originally put the provider fiber on the cache context because I expected the semantics to be that a refresh finds the root of the "freshness" boundary; that is, all the data that refreshed or appeared as par...
Succeeded
#83985
Remove provider fiber from cache context I originally put the provider fiber on the cache context because I expected the semantics to be that a refresh finds the root of the "freshness" boundary; that is, all the data that refreshed or appeared as par...
Succeeded
#83981
Only mutate `root.pooledCache` in complete/unwind Less indirection when accessing during the render phase and less hard to make a mutation mistake.
Succeeded
#83979
Only mutate `root.pooledCache` in complete/unwind Less indirection when accessing during the render phase and less hard to make a mutation mistake.
Succeeded
#83978
Only mutate `root.pooledCache` in complete/unwind Less indirection when accessing during the render phase and less hard to make a mutation mistake.
Succeeded
#83929
Remove default transition priority for refreshes The flaw here is that if another update in the same event is not wrapped in `startTransition`, then it won't be batched with the refresh. The solution is to wrap both in the same `startTransition`. It's...
Succeeded
#83918
Wrap more things in flag
Succeeded
#83916
Wrap more things in flag
Succeeded
#83844
More tests
Succeeded
#83720
More tests
Succeeded
#83693
useRefresh -> useCacheRefresh useRefresh is probably too general. We may also add additional APIs related to the cache, and including the word "cache" in all of them signals they are related.
Succeeded
#83687
Use only a single pooled cache at a time The cache-per-lane approach makes conceptual sense but it's probably not worth it until we complete the Lanes entanglement refactor. In the current implementation we have to do lots of looping to maintain the p...
Succeeded
#83651
Previous retry cache takes precedence over pool When committing a fallback, if there's no cache on the stack, check if there's a cache from the previous render. This is what we would have used for new content during the first pass when we attempted to...
Succeeded
#83637
Remove useRefresh from unstable-shared-subset From @sebmarkbage's comment > This should not be included in this file. Which means that the error > the dispatcher throws should never be reachable, but worth keep in > case something is misconfigured or...
Succeeded
#83636
Remove useRefresh from unstable-shared-subset From @sebmarkbage's comment > This should not be included in this file. Which means that the error > the dispatcher throws should never be reachable, but worth keep in > case something is misconfigured or...
Succeeded
#83634
Code size optimizations - Wraped more things in the feature flag. - Removed CacheComponent cases from commit phase.
Succeeded
#83625
Restore retry cache from Suspense/Offscreen fiber When a Suspense or Offscreen boundary resumes rendering, the inner tree should use the same cache that the outer one did during the original render. This is important not just for UI consistency reason...
Succeeded
#83401
Restore retry cache from Suspense/Offscreen fiber When a Suspense or Offscreen boundary resumes rendering, the inner tree should use the same cache that the outer one did during the original render. This is important not just for UI consistency reason...
Succeeded
#83323
Explicitly check if the parent provider is fresh We can track this cheaply because there's only ever a single fresh provider. We don't need to store the fresh caches on the stack, just one if it exists. Then when we unwind the Fiber stack, we reset it...
Canceled
#83322
Explicitly check if the parent provider is fresh We can track this cheaply because there's only ever a single fresh provider. We don't need to store the fresh caches on the stack, just one if it exists. Then when we unwind the Fiber stack, we reset it...
Succeeded
#83320
Explicitly check if the parent provider is fresh We can track this cheaply because there's only ever a single fresh provider. We don't need to store the fresh caches on the stack, just one if it exists. Then when we unwind the Fiber stack, we reset it...
Canceled
#83319
Explicitly check if the parent provider is fresh We can track this cheaply because there's only ever a single fresh provider. We don't need to store the fresh caches on the stack, just one if it exists. Then when we unwind the Fiber stack, we reset it...
Succeeded
#83027
Every request in initial render shares same cache I noticed this bug when writing some new tests. The HostRoot fiber is special because it's always mounted. The moment you call `createRoot()`, you have a "current" (albeit empty) tree. So the "initial...
Succeeded
#83011
Add fast path for nested mounting Caches Only the top most Cache boundary in a newly mounting tree needs to call `requestFreshCache`. Nested caches can inherit the parent cache by reading from context. This is strictly a performance optimization, sin...
Canceled
#83010
Use an update queue for refreshes Refreshes are easier than initial mounts because we have a mounted fiber that we can attach the cache to. We don't need to rely on clever pooling tricks; they're just normal updates. More importantly, we're not at ri...
Succeeded
#82999
Add fast path for nested mounting Caches Only the top most Cache boundary in a newly mounting tree needs to call `requestFreshCache`. Nested caches can inherit the parent cache by reading from context. This is strictly a performance optimization, sin...
Succeeded
#82996
Use an update queue for refreshes Refreshes are easier than initial mounts because we have a mounted fiber that we can attach the cache to. We don't need to rely on clever pooling tricks; they're just normal updates. More importantly, we're not at ri...
Succeeded
#82994
Use an update queue for refreshes Refreshes are easier than initial mounts because we have a mounted fiber that we can attach the cache to. We don't need to rely on clever pooling tricks; they're just normal updates. More importantly, we're not at ri...
Failed
#82993
Use an update queue for refreshes Refreshes are easier than initial mounts because we have a mounted fiber that we can attach the cache to. We don't need to rely on clever pooling tricks; they're just normal updates. More importantly, we're not at ri...
Succeeded
#82975
Add implicit root-level cache If `getCacheForType` or `useRefresh` cannot find a parent <Cache />, they will access a top-level cache associated with the root. The behavior is effectively the same as if you wrapped the entire tree in a <Cache /> bound...
Failed
#82974
Add implicit root-level cache If `getCacheForType` or `useRefresh` cannot find a parent <Cache />, they will access a top-level cache associated with the root. The behavior is effectively the same as if you wrapped the entire tree in a <Cache /> bound...
Succeeded
#82963
Refreshes should not affect "sibling" boundaries I had thought we decided that refreshing a boundary would also refresh all the content that is currently consistent (i.e. shared the same underlying cache) with it, but I was wrong. Refreshing should on...
Succeeded
#82876
Refresh with seeded data Usually, when performing a server mutation, the response includes an updated version of the mutated data. This avoids an extra roundtrip, and because of eventual consistency, it also guarantees that we reload with the freshes...
Succeeded
#82716
Cache refreshing Implements useRefresh, a method to invalidate the cache and request new data. It will find the nearest <Cache /> boundary, clear its cache, and schedule an update to re-render with fresh data. We had discussed calling this method `u...
Succeeded
#82712
Cache refreshing Implements useRefresh, a method to invalidate the cache and request new data. It will find the nearest <Cache /> boundary, clear its cache, and schedule an update to re-render with fresh data. We had discussed calling this method `u...
Canceled
#82701
Cache refreshing Implements useRefresh, a method to invalidate the cache and request new data. It will find the nearest <Cache /> boundary, clear its cache, and schedule an update to re-render with fresh data. We had discussed calling this method `u...
Succeeded
#82688
Cache refreshing Implements useRefresh, a method to invalidate the cache and request new data. It will find the nearest <Cache /> boundary, clear its cache, and schedule an update to re-render with fresh data. We had discussed calling this method `u...
Succeeded

facebook/react    #84244

Started duration: 03:01
acdlite opened pull request #20456 to master
Loading Sandboxes...
Loading Packages...
Loading Install Instructions...
Finished!
Loading...