Azure / Azure/durabletask

Emulator hangs indefinitely instead of throwing expected error

Offen
#447 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
bug
Vorherrschende Sprache
C#
Sterne
1.7k
Forks
335
Ø Merge
2 T. 23 Std.
Gemergte PRs (30 T.)
6

Beschreibung

Using the LocalOrchestrationService, if I create an orchestration instance and allow it to finish, then try creating another instance using the same id, the call to `CreateOrchestrationInstanceAsync` ends up hanging indefinitely. The same code with the ServiceBusOrchestrationService plugged in instead throws the expected error message: "An orchestration with id 'x' already exists. It is in state Completed".

Interestingly, if I don't wait for the first instance to finish and start the second instance immediately, I see the expected error message using the LocalOrchestrationService: "An orchestration with id 'x' already exists. It is in state Pending".

Here's a gist of the code I used to create the issue: https://gist.github.com/maxnorth/a9a860f86425c4890e01f3deb9307b69

I'm using these nuget packages:
Microsoft.Azure.DurableFramework.Core: **2.4.1**
Microsoft.Azure.DurableFramework.Emulator: **2.2.5**

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

Start with LocalOrchestrationService and the CreateOrchestrationInstanceAsync entry point described in the issue. Reproduce the sequence from the linked gist, comparing a completed orchestration with a pending one and with ServiceBusOrchestrationService. Done means the completed-instance case returns the expected duplicate-id error instead of hanging.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
csharp
Bereich
backend, distributed-systems
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.