Skip to content

Unexpected behavior for failing asset downloads #1969

Description

@rustyy

Actual behavior

If an asset can not be downloaded during export the following issues come up:

  • the error is shown in the result table, but the export is still assumed to be successful, even no error-log is created
  • starting with version 7.21.12 - if an error occurs during download, the export process runs forever (could not be reproduced with versions <=7.21.11)
Image

Expected behavior

  • in case of an error an error-log is created and the export is not treated as successful
  • in case of an error once the export is finished the process shuts down

Tested environments

  • Linux Ubuntu 22.04, Node 20.18.2
  • Linux Ubuntu 22.04, Node 22.13.1
  • MacOS 15.3, Node 20.18.2
  • MacOS 15.3 Node 22.13.1

Steps to reproduce

The simplest way to reproduce is to archive an asset and set the "includeArchived"-option to true in the export function.
As requesting archived assets will end up in 404, an error will be present.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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