Skip to content

Bad request definition can cause convertRequests to hang #39

@JoshMock

Description

@JoshMock

I was using the new JS converter to update all the examples in the JS client repo, and convertRequests kept hanging on bad request definitions that look like:

{
  "took": 17,
  "timed_out": false,
  "_shards": {
    "total": 4,
    "successful": 4,
    "skipped": 0,
    "failed": 0
  },
  "hits": {
    "total": {
      "value": 10,
      "relation": "eq"
    },
...

I'm not sure yet if it's the lack of an HTTP verb, or the fact that it's incomplete and ends with ..., but it causes the function's promise to never resolve.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions