inlife/nexrender

Bad error logging if asset could not be downloaded

schubc opened this issue · 0 comments

Describe the bug
If an asset can not be downloaded, only the string [object Object] is sent as error text

Information about environment

  • Which version of nexrender are you using?
  • current version, binary, npm and current main branch
  • What kind of the setup do you have? (server+worker or cli)
  • server+worker
    Expected behavior

If an asset cannot be downloaded, it should be logged to nexrender-server. Currently only [object Object] is logged.

example:
image2.jpg returned a 404 error

[
  {
    "uid": "deadbeef",
    "type": "default",
    "state": "error",
    "output": "",
    "tags": null,
    "priority": 0,
    "template": {
      "src": "https://example.com/scene.aep",
      "composition": "myComposition",
      "outputModule": "My-Output-Module",
      "outputExt": "mp4",
      "settingsTemplate": "My-Settings-Template"
    },
    "assets": [
      {
        "src": "https://example.com/assets.zip",
        "type": "static"
      },
      {
        "src": "https://example.com/image1.jpg",
        "composition": "myComposition",
        "layerName": "myLayer1",
        "type": "image",
        "dest": ""
      },
      {
        "src": "https://example.com/image2.jpg",
        "composition": "myComposition",
        "layerName": "myLayer2",
        "type": "image",
        "dest": ""
      }
    ],
    "error": "[object Object]"
  }
]

I changed the Error handling in #1001