I'm submitting a...

[ ] Regression 

Bug Report

Current behavior

Adding the following decorator, where status is optional according to the TS typings, produces an open API spec with an undefined response code. This causes issues with the generated docs, as well as code generators that consume open API.

  @ApiResponse({
    description:
      'Updates a Cat',
  })

The open API spec generated looks s

Hi, I'm a relative novice when it comes to this type of thing, however I have setup HomeBridge on my mac and happily access my Nest Cams in the Home app on MacOS and IOS - to do this I installed ffmpeg etc. I am familiar with creating .json files etc and executing commands in the terminal but this is about the extent of my knowledge.

Would anyone be good enough to provide a simple, high-level

In case common C++ exceptions are raised somewhere in the NEST code, they are caught by the SLI main loop, and presented to users by printing only the name of the exception. For most exceptions this is probably an appropriate course of action. One where it probably isn't, is std::bad_alloc, which signals an out-of-memory condition. Recently, there were multiple reports on the mailing list relate