You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whilst working on #203 I've noticed that the PR #251 has introduced failures into the EmulatorFunctionalTests, namely MockGenerationTest and MockRecreateOrchestrationTest.
This manifests as a timeout, but the underlying issue is the orchestration is continually retrying due to a corrupt state where there are Multiple ExecutionCompletedEvents in the history.
I managed to trace the issue down to something to do with the OrchestrationRuntimeState being passed in to CompleteTaskOrchestrationWorkItemAsync inside DurableTask.Core.TaskOrchestrationDispatcher.OnProcessWorkItemAsync (Line #402 on master as of this issue). Perhaps the local orchestration service wasn't properly updated to deal with the new raised event fix?
I won't have time to look at this for another few days, so I thought I'd just post my findings here.
The text was updated successfully, but these errors were encountered:
Whilst working on #203 I've noticed that the PR #251 has introduced failures into the
EmulatorFunctionalTests
, namelyMockGenerationTest
andMockRecreateOrchestrationTest
.This manifests as a timeout, but the underlying issue is the orchestration is continually retrying due to a corrupt state where there are Multiple ExecutionCompletedEvents in the history.
I managed to trace the issue down to something to do with the
OrchestrationRuntimeState
being passed in toCompleteTaskOrchestrationWorkItemAsync
insideDurableTask.Core.TaskOrchestrationDispatcher.OnProcessWorkItemAsync
(Line #402 onmaster
as of this issue). Perhaps the local orchestration service wasn't properly updated to deal with the new raised event fix?I won't have time to look at this for another few days, so I thought I'd just post my findings here.
The text was updated successfully, but these errors were encountered: