Skip to content

Conversation

@AArnott
Copy link
Member

@AArnott AArnott commented Jan 11, 2024

The bug description is found in #983.

The fix is simply to share the JoinableTask "token" across JsonRpc instances. We correlate JoinableTask tokens across JsonRpc instances (by default).

Mutable statics are more or less likely to cause problems with testing or advanced product scenarios. In this case though, it seems very likely that every shipping scenario will be drastically simpler by defaulting to sharing state across instances, so that is the default. Advanced cases can opt into isolating those instances however, and I have a test to verify this.

Fixes #983

Mutable statics are more or less likely to cause problems with testing or advanced product scenarios. In this case though, it seems *very* likely that every shipping scenario will be drastically simpler by defaulting to sharing state across instances, so that is the default. Advanced cases can opt into isolating those instances however, and I have a test to verify this.

Fixes microsoft#983
@AArnott AArnott added this to the v2.18 milestone Jan 11, 2024
@AArnott AArnott requested a review from RyanToth3 January 11, 2024 03:52
@AArnott AArnott enabled auto-merge January 11, 2024 03:52
@AArnott AArnott merged commit 78da8ab into microsoft:main Jan 11, 2024
@AArnott AArnott deleted the fix983 branch January 11, 2024 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

JoinableTaskFactory bridge fails with multiple JsonRpc instances in a process without JTF

3 participants