{
    "properties": {
      "thumbnail_id": {
        "type": "keyword"
      },
      "path": {
        "type": "keyword"
      },
      "generator": {
        "type": "keyword"
      },
      "target": {
        "type": "keyword"
      },
      "createdTime": {
        "type": "long"
      },
      "createdBy": {
        "type": "keyword"
      }
    }

direct YAML support in the API available today), the Content-Type and Accept
headers are now properly handled as per the HTTP spec.  As a consequence, if
you had a client that was sending an invalid Content-Type or Accept header to
the API, in 1.2 you will either receive a 415 or 406 error.
The only client
this is known to affect is curl when you use -d with JSON but don't set a
content type, helpfully sends "application/x-www-urlencoded", which is not

        "properties" : {
          "createdBy" : {
            "type" : "keyword"
          },
          "createdTime" : {
            "type" : "long"
          },
          "generator" : {
            "type" : "keyword"
          },
          "path" : {
            "type" : "keyword"
          },
          "target" : {
            "type" : "keyword"
          },
          "thumbnail_id" : {

      required: true

  - type: textarea
    id: since
    attributes:
      label: Since when has it been failing?
    validations:
      required: true

  - type: input
    id: testgrid
    attributes:
      label: Testgrid link

  - type: textarea
    id: reason
    attributes:
      label: Reason for failure (if possible)

  - type: textarea
    id: additional
    attributes:

        assertTrue(ssoException instanceof Throwable);
    }

    @Test
    public void test_constructor_withVariousExceptionTypes() {
        // Test constructor with different exception types as cause
        String message = "SSO process failed";

        // Test with IOException
        Exception ioException = new java.io.IOException("Connection refused");

      },
      "stopword_en_filter": {
        "type": "stop",
        "stopwords": "_english_"
      },
      "content_length_filter": {
        "type": "length",
        "max": 30
      },
      "limit_token_count_filter": {
        "type": "limit",
        "max_token_count": 2147483647
      },
      "stemmer_en_filter": {
        "type": "stemmer",
        "name": "english"
      },

      },
      "favorite_count": {
        "type": "long"
      },
      "filename": {
        "type": "keyword"
      },
      "filetype": {
        "type": "keyword"
      },
      "host": {
        "type": "keyword"
      },
      "lang": {
        "type": "keyword"
      },
      "last_modified": {
        "type": "date",
        "format": "date_optional_time"
      },

    assume().that(graph.incidentEdgeOrder().type()).isEqualTo(ElementOrder.Type.STABLE);

    populateTShapedGraph();

    assertThat(graph.adjacentNodes(1)).containsExactly(2, 4, 3).inOrder();
  }

  @Test
  public void stableIncidentEdgeOrder_predecessors_returnsInConnectingEdgeInsertionOrder() {
    assume().that(graph.incidentEdgeOrder().type()).isEqualTo(ElementOrder.Type.STABLE);

    populateTShapedGraph();

                                                <button type="button" class="btn btn-outline-dark"
                                                        data-dismiss="modal">
                                                    <la:message key="labels.crud_button_cancel"/>
                                                </button>
                                                <button type="submit" class="btn btn-outline-dark"

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code