TimeoutInfo.lastValue is null when it shouldn't be

[cyber-barrista]

Describe the bug

TimeoutInfo is an object that is passed to the with callback of TimeoutConfig (timeout operator's config object). It has lastValue field which seems to be null regardless of what was the last value emitted before the timeout occurred.

Expected behavior

lastValue is expected to contain a value emitted right before the timeout firing.

Reproduction code

import { interval, concat, take, EMPTY, timeout } from 'rxjs';

const fast = interval(10).pipe(take(5));
const slow = interval(1000).pipe(take(5));

const replacement = info => {console.log(info); return EMPTY }

const withTimeout = concat(fast, slow).pipe(timeout({each: 500, with: replacement}))

withTimeout.subscribe(console.log);

Reproduction URL

No response

Version

7.8.1

Environment

Browser (V8)

Additional context

Looks like this line

rxjs/src/internal/operators/timeout.ts

Line 362 in 3859f86

lastValue = null;

is the one to blame

[benlesh]

Hi @cyber-barrista — thank you for taking the time to open this issue and for sharing your thoughtful feedback with the RxJS project. I’m sorry it took us so long to respond. Given how much time has passed and the lack of recent activity, I’m going to close this for now so the tracker reflects the work we’re likely to act on. If this is still relevant on a current RxJS release, please feel welcome to open a new issue with updated context and a reproduction. Thank you again for your contribution and patience.

— Ben