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
{{ message }}
This repository has been archived by the owner on Jun 28, 2022. It is now read-only.
In CreateWorkspace.cs line 32 the method definition is marked async, however, there is no await call in the method body.
This would be a quick fix to add the await keyword, however, the async call on line 77 returns an object, ProcessOperationResult, which returns a compiler error when using the await keyword,
'ProcessOperationResult' does not contain a definition for 'GetAwaiter'
This may indicate a defect, not in this source code, but in the API call not being properly async:
After further investigation, I've discovered that the API call, although async in nature, is not architected in an async manner I'm familiar with. While the workspace does appear to be created in a separate thread, in order for our code to remain async we must subscribe to the proxy's event listeners. The definition of this method ought not to be async since we are blocking the execution to wait for the ProcessState to return Completed.
In CreateWorkspace.cs line 32 the method definition is marked async, however, there is no await call in the method body.
This would be a quick fix to add the await keyword, however, the async call on line 77 returns an object, ProcessOperationResult, which returns a compiler error when using the await keyword,
'ProcessOperationResult' does not contain a definition for 'GetAwaiter'
This may indicate a defect, not in this source code, but in the API call not being properly async:
proxy.Repositories.Workspace.CreateAsync(templateArtifactID, workspaceDTO);
The text was updated successfully, but these errors were encountered: