Skip to content

Commit

Permalink
Revert "Bugfix: Expiring a partially completed tree (#17926)" (#17941)
Browse files Browse the repository at this point in the history
This reverts commit 01974a8.

* Failing test: Expiring a partially completed tree

We should not throw out a partially completed tree if it expires in the
middle of rendering. We should finish the rest of the tree without
yielding, then finish any remaining expired levels in a single batch.

* Check if there's a partial tree before restarting

If a partial render expires, we should stay in the concurrent path
(performConcurrentWorkOnRoot); we'll stop yielding, but the rest of the
behavior remains the same.

We will only revert to the sync path (performSyncWorkOnRoot) when
starting on a new level.

This approach prevents partially completed concurrent work from
being discarded.

* New test: retry after error during expired render
  • Loading branch information
acdlite committed Jan 30, 2020
1 parent d2ae77d commit 9dbe1c5
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 169 deletions.
13 changes: 3 additions & 10 deletions packages/react-reconciler/src/ReactFiberWorkLoop.js
Expand Up @@ -644,16 +644,9 @@ function performConcurrentWorkOnRoot(root, didTimeout) {
// event time. The next update will compute a new event time.
currentEventTime = NoWork;

// Check if the render expired. If so, restart at the current time so that we
// can finish all the expired work in a single batch. However, we should only
// do this if we're starting a new tree. If we're in the middle of an existing
// tree, we'll continue working on that (without yielding) so that the work
// doesn't get dropped. If there's another expired level after that, we'll hit
// this path again, at which point we can batch all the subsequent levels
// together.
if (didTimeout && workInProgress === null) {
// Mark the current time as expired to synchronously render all expired work
// in a single batch.
if (didTimeout) {
// The render task took too long to complete. Mark the current time as
// expired to synchronously render all expired work in a single batch.
const currentTime = requestCurrentTimeForUpdate();
markRootExpiredAtTime(root, currentTime);
// This will schedule a synchronous callback.
Expand Down
Expand Up @@ -381,55 +381,6 @@ describe('ReactIncrementalErrorHandling', () => {
expect(ReactNoop.getChildren()).toEqual([]);
});

it('retries one more time if an error occurs during a render that expires midway through the tree', () => {
function Oops() {
Scheduler.unstable_yieldValue('Oops');
throw new Error('Oops');
}

function Text({text}) {
Scheduler.unstable_yieldValue(text);
return text;
}

function App() {
return (
<>
<Text text="A" />
<Text text="B" />
<Oops />
<Text text="C" />
<Text text="D" />
</>
);
}

ReactNoop.render(<App />);

// Render part of the tree
expect(Scheduler).toFlushAndYieldThrough(['A', 'B']);

// Expire the render midway through
expect(() => ReactNoop.expire(10000)).toThrow('Oops');

expect(Scheduler).toHaveYielded([
// The render expired, but we shouldn't throw out the partial work.
// Finish the current level.
'Oops',
'C',
'D',

// Since the error occured during a partially concurrent render, we should
// retry one more time, synchonrously.
'A',
'B',
'Oops',
'C',
'D',
]);
expect(ReactNoop.getChildren()).toEqual([]);
});

it('calls componentDidCatch multiple times for multiple errors', () => {
let id = 0;
class BadMount extends React.Component {
Expand Down
Expand Up @@ -655,116 +655,6 @@ describe('ReactIncrementalUpdates', () => {
});
});

it('does not throw out partially completed tree if it expires midway through', () => {
function Text({text}) {
Scheduler.unstable_yieldValue(text);
return text;
}

function App({step}) {
return (
<>
<Text text={`A${step}`} />
<Text text={`B${step}`} />
<Text text={`C${step}`} />
</>
);
}

function interrupt() {
ReactNoop.flushSync(() => {
ReactNoop.renderToRootWithID(null, 'other-root');
});
}

// First, as a sanity check, assert what happens when four low pri
// updates in separate batches are all flushed in the same callback
ReactNoop.act(() => {
ReactNoop.render(<App step={1} />);
Scheduler.unstable_advanceTime(1000);
expect(Scheduler).toFlushAndYieldThrough(['A1']);

interrupt();

ReactNoop.render(<App step={2} />);
Scheduler.unstable_advanceTime(1000);
expect(Scheduler).toFlushAndYieldThrough(['A1']);

interrupt();

ReactNoop.render(<App step={3} />);
Scheduler.unstable_advanceTime(1000);
expect(Scheduler).toFlushAndYieldThrough(['A1']);

interrupt();

ReactNoop.render(<App step={4} />);
Scheduler.unstable_advanceTime(1000);
expect(Scheduler).toFlushAndYieldThrough(['A1']);

// Each update flushes in a separate commit.
// Note: This isn't necessarily the ideal behavior. It might be better to
// batch all of these updates together. The fact that they don't is an
// implementation detail. The important part of this unit test is what
// happens when they expire, in which case they really should be batched to
// avoid blocking the main thread for a long time.
expect(Scheduler).toFlushAndYield([
// A1 already completed. Finish rendering the first level.
'B1',
'C1',
// The remaining two levels complete sequentially.
'A2',
'B2',
'C2',
'A3',
'B3',
'C3',
'A4',
'B4',
'C4',
]);
});

ReactNoop.act(() => {
// Now do the same thing over again, but this time, expire all the updates
// instead of flushing them normally.
ReactNoop.render(<App step={1} />);
Scheduler.unstable_advanceTime(1000);
expect(Scheduler).toFlushAndYieldThrough(['A1']);

interrupt();

ReactNoop.render(<App step={2} />);
Scheduler.unstable_advanceTime(1000);
expect(Scheduler).toFlushAndYieldThrough(['A1']);

interrupt();

ReactNoop.render(<App step={3} />);
Scheduler.unstable_advanceTime(1000);
expect(Scheduler).toFlushAndYieldThrough(['A1']);

interrupt();

ReactNoop.render(<App step={4} />);
Scheduler.unstable_advanceTime(1000);
expect(Scheduler).toFlushAndYieldThrough(['A1']);

// Expire all the updates
ReactNoop.expire(10000);

expect(Scheduler).toHaveYielded([
// A1 already completed. Finish rendering the first level.
'B1',
'C1',
// Then render the remaining two levels in a single batch
'A4',
'B4',
'C4',
]);
});
});

it('when rebasing, does not exclude updates that were already committed, regardless of priority', async () => {
const {useState, useLayoutEffect} = React;

Expand Down

0 comments on commit 9dbe1c5

Please sign in to comment.