-
According to the [documentation on error handling](https://docs.microsoft.com/en-us/aspnet/core/web-api/handle-errors?view=aspnetcore-3.1) Two steps are needed to handle errors in asp.net core web api…
-
In most places error callbacks receive only descriptions of the error that occurred. In order to map errors then, we need to do string matching which is a pretty brittle approach. It would be useful t…
-
Inspired by #73 :
According to [RFC 7231](https://tools.ietf.org/html/rfc7231):
> The 406 (Not Acceptable) status code indicates that the target resource does not have a current representation…
-
Backward compatibility is a necessary part of storage infrastructure, but we'd like to minimize the associated technical debt. Initially our migrations were one-off, required complicated reasoning, an…
-
## In what area(s)?
/area runtime
## Background
Daprized application can communicates with the other applications. Application exposes HTTP/1.1 and gRPC endpoints and calls HTTP/1.1 and g…
-
- [ ] Use custom error types to differentiate errors throughout the code base (as well as allow us to use different behaviours according to the type of the error). This can be an interesting resource:…
-
There is a RFC about default response type for API's in case of error.
> Abstract
This document defines a "problem detail" as a way to carry machine-
readable details of errors in a HTTP re…
-
Output of `curl -s cht.sh/~docker-compose` is too long, because the whole `:list` output is printed. Maybe show just a few lines of context for it?
```
[:list]
...
docker-build
docker-compose
do…
-
Output of `curl -s cht.sh/~docker-compose` is too long, because the whole `:list` output is printed. Maybe show just a few lines of context for it?
```
[:list]
...
docker-build
docker-compose
do…
-
Howdy!
I love the idea of this repository. We have tons of GCP Cloud Functions and Cloud Runs (what an awful noun). It can be hard for a dev to switch between the two, particularly to go to Cloud R…