Is 'TrySaveStateAsync's throwing on 412 response an intended behaviour?
Open
area/client/state
kind/bug
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 378
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 5
Description
Hello
I'm just started using Dapr and found this really odd that the method 'TrySaveStateAsync' is throwing and not simply returning false when it faces newer etag in db. I'm using Cosmos db in local emulator, and here's how I tested it(I know that code on the screen should read new value before re-trying, just wanted to test the behaviour):
Is that intended or am I doing something wrong here?
Contributor guide
Assessment
This issue has not been assessed yet.