Change in behaviour of ToObservableChangeSet with expireAfter in v6.14.*

[aguahombre]

The ToObservableChangeSet expireAfter no longer works in v6.14.* if the the source IObservable<IEnumerable> completes before the timeout occurs.

Using this example compiled with v6.13.21 using .netcore 3.1 console program on Windows 10

static void Main(string[] args)
{
    Observable.Return(Enumerable.Range(0, 10).Select(i => new { A = i, B = 2 * i }))
        .ToObservableChangeSet(x => x.A, _ => TimeSpan.FromSeconds(5))
        .Subscribe(x => Console.WriteLine($"{DateTime.UtcNow} {x.Count}:\n  {string.Join("\n  ", x)}"));
    Console.ReadKey();
}

produces the output

but with v6.14.18

I would expect the v6.13.21 behaviour to occur; i.e. the items to be removed from the change set after 5 seconds.

[RLittlesII]

@aguahombre Thank you for providing this report. We will look into it and provide and update.

Also, is there a list of dependent libraries and their versions per test execution?

[aguahombre]

Here is the project file

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp3.1</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="DynamicData" Version="6.14.18" />
  </ItemGroup>

</Project>

and the using statements

using System;
using System.Linq;
using System.Reactive.Linq;
using DynamicData;

[RolandPheasant]

It's been long overdue for me looking at this. But the change which creates there error was introduced in the commit.

It's not obvious why this would be an issue but I'll take a look. Ideally it can be reproduced in a unit test.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.