Upgrading from Microsoft.Azure.WebJobs.Extensions.DurableTask Version= 2.3.1 to version 2.4.0 creates compile conflict with System.Reactive 4.4.0

[Arash-Sabet]

Description

Create a function project and reference both nuget packages mentioned in the title of this ticket. Write a piece of code like the following snippet:

IObservable<T>.Subscribe(
				onNext: _ =>
				{
					//do something
				},
				onError: exception =>
				{
					//do something
				},
				onCompleted: () =>
				{
					//do something
				});

You will get the following compile error:

Error | CS0121 | The call is ambiguous between the following methods or properties: 'System.ObservableExtensions.Subscribe(System.IObservable, System.Action, System.Action<System.Exception>, System.Action)' and 'System.ObservableExtensions.Subscribe(System.IObservable, System.Action, System.Action<System.Exception>, System.Action)' |

Expected behavior

There should not be a compile error.

Actual behavior

The compile error quoted above happens.

Relevant source code snippets

Already shared.

Known workarounds

None

App Details

• Durable Functions extension version 2.4.0:
• Azure Functions runtime version 3.1:
• Programming language used: C#

Screenshots

n/a

If deployed to Azure

No

[Arash-Sabet]

@cgillum Could you please have someone look into this issue? I have had to revert to version 2.3.1 of Microsoft.Azure.WebJobs.Extensions.DurableTask to avoid this conflict.

[Arash-Sabet]

@anthonychu Would you please let me know who the best person is to escalate this issue to? This issue is a blocker to progress further.

[ConnorMcMahon]

@Arash-Sabet

So this looks like due to a dependency taken by DurableTask.Core (v2.5.0) on System.Reactive.Core v3.x. I don't think this dependency is required, as it builds without it, so we can likely remove this in a subsequent release.

As a workaround in the meantime, I found this stackoverflow answer. You can either force System.Reactive.Core up to v4 by explicitly including it with v4.4.1 in your csproj, or you can use System.Reactive.Compatibility nuget package to resolve the issue.

[Arash-Sabet]

@Arash-Sabet

So this looks like due to a dependency taken by DurableTask.Core (v2.5.0) on System.Reactive.Core v3.x. I don't think this dependency is required, as it builds without it, so we can likely remove this in a subsequent release.

As a workaround in the meantime, I found this stackoverflow answer. You can either force System.Reactive.Core up to v4 by explicitly including it with v4.4.1 in your csproj, or you can use System.Reactive.Compatibility nuget package to resolve the issue.

Thanks. I will have the workaround given a try. When do you think the new subsequent release will be ready after the removal of the dependency?

[ConnorMcMahon]

Currently targeting code freeze of tomorrow, release by January 20th.

[ConnorMcMahon]

It turns out that System.Reactive.Core is required now by DurableTask.Core, so we will be adding System.Reactive.Compatibility as well to avoid the conflict.

[Arash-Sabet]

The workaround caused some other changes in our code which are vaster than one area. A lot of changes need to be done in referenced libraries and therefore nuget packages to be updated and deployed. So, we have to wait for the new release by Microsoft. @ConnorMcMahon

[davidmrdavid]

Closing because the corresponding PR has been merged ⚡ ⚡