Releases: dapr/dotnet-sdk
Releases · dapr/dotnet-sdk
Dapr dotnet-sdk v1.6.0
Fix issue where state did not reset on actor error (#789) When an actor call fails, it is imperative that the state is reset. In the remoting path, we were catching the exception and returning an error response instead of propagating the exception. Without this, the error path was never triggered. This allowed for state from failed requests to persist on subsequent requests. https://github.com/dapr/dotnet-sdk/issues/762 Signed-off-by: Hal Spang <[email protected]>
Dapr dotnet-sdk v1.6.0-rc01 (Pre-release)
Fix issue where state did not reset on actor error (#789) When an actor call fails, it is imperative that the state is reset. In the remoting path, we were catching the exception and returning an error response instead of propagating the exception. Without this, the error path was never triggered. This allowed for state from failed requests to persist on subsequent requests. https://github.com/dapr/dotnet-sdk/issues/762 Signed-off-by: Hal Spang <[email protected]>
Dapr dotnet-sdk v1.5.0
Allow multiple topics to call the same endpoint (#763) * Allow multiple topics to call the same endpoint Using the WithTopic builder pattern allows you to specify multiple topics that route to a single endpoint. Given the topics are unique, this should be a valid case. This change allows for a single endpoint to bind to multiple topics. Note that this can only be done via the EndpointBuilder and not the TopicAttribute. https://github.com/dapr/dotnet-sdk/issues/715 * Let TopicAttribute to be specified multiple times The endpoint builder allowed for multiple WithTopic calls so the attribute should match that behavior.
Dapr dotnet-sdk v1.4.0
Add an option to set Timeout for ActorProxy (#748) * Add an option to set Timeout for ActorProxy Actors, by there nature, may have to wait for a long period before being allowed to execute. This could lead to long request times. The default timeout for the HttpClient being used is fairly low. This commit allows for the timeout to be set when constructing the proxy. https://github.com/dapr/dotnet-sdk/issues/728 * Removed extra constructor and e2e tests.
Dapr dotnet-sdk v1.4.0-rc (prerelease)
Add an option to set Timeout for ActorProxy (#748) * Add an option to set Timeout for ActorProxy Actors, by there nature, may have to wait for a long period before being allowed to execute. This could lead to long request times. The default timeout for the HttpClient being used is fairly low. This commit allows for the timeout to be set when constructing the proxy. https://github.com/dapr/dotnet-sdk/issues/728 * Removed extra constructor and e2e tests.
Dapr dotnet-sdk v1.3.0
Only isolate state when using reentrancy (#723) Non-reentrant actors can utilize their state manager's cache for repeated calls. They should still be able to do this unless using reentrancy. Co-authored-by: Ryan Nowak <[email protected]>
v1.2.0 release
Merge pull request #673 from jasonviviano/jasonviviano/typo-fix Fix Typo
Dapr dotnet SDK v
Release dapr dotnet SDK v
Dapr dotnet SDK v1.0.0
Release dapr dotnet SDK v1.0.0
Dapr dotnet SDK v1.0.0-rc06
Release dapr dotnet SDK v1.0.0-rc06