-
Error sources as currently defined do not provide a mechanism to specify errors resulting from invalid HTTP headers. Adding a `header` field would satisfy this use case:
> * `source`: an object con…
-
##### Description
We see that inheritance (instead of composition) is generated where, as we think, it should not.
Namely, we have the following model file:
```yml
openapi: "3.0.2"
info:
…
-
**Symfony version(s) affected**: 4.4.12
**Description**
I am using the HTTP client to query a third party API. I am making a call that results in a 400 Bad Request response, and the response l…
-
# Problem description
I'm extending the admin area with custom entities and having issues setting unique fields. The unique check works but it's completely hidden for the user.
On the screenshoots I…
-
I had opened a [issue](https://github.com/grpc/grpc-dotnet/issues/1011) some time ago, but I believe that it was not very clear.
I dont was able to participate in the discussion because I w…
-
### Describe the bug
During Unit Tests, I was getting a NullReferenceExeption in ControllerBase.ValidationProblem. Difficult to narrow down the problem.
### To Reproduce
Steps to reproduce the be…
-
We should ensure that all errors returned by the API follow the same structure and have an appropriate error response code. For the base structure, I'd propose RFC 7807:
```json
{
"type": "http…
-
On error, the v2 API reports a JSON text along with the status code. The exact format isn't clear, but it has the general shape:
```json
{
"errors": [ {"message": "you done broke it", "code": 4…
-
The following **BATCH** operation correctly identifies the `@context` to be missing:
```console
curl -L -X POST 'http://localhost:9090/ngsi-ld/v1/entityOperations/upsert?options=update' \
-H 'Con…
-
I detected the following -- IMHO wrong -- behavior change between releases 9.4.20 and 9.4.21.
Given this trivial servlet:
```java
package org.cstamas.jetty.bug;
import java.io.IOException;
…