Emulator hangs indefinitely instead of throwing expected error
- Lingua principale
- C#
- Stelle
- 1.7k
- Fork
- 335
- Merge medio
- 2g 23h
- PR unite (30g)
- 6
Descrizione
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**
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- csharp
- Ambito
- backend, distributed-systems
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100