Skip to content

List of files to process may be larger than it should be #33

Description

@regan-sarwas

Try this:

  • Update an Argos deployment start date from null to non null: some results files will be deleted, and issues created (file will not be reprocessed due to issues)
  • update the deployment start date back to null: the issues will be deleted, and the files will be listed for reprocessing
  • update the deployment start date back to non-null: issues will not get created (issue generation is based of deleting results files), so all files will be available for reprocessing (however some cannot be because they have no deployment)

I think there is a bug here: the list of files to process should not include those without a valid deployment.

I tried to fix this, and ran out of time. This is not a major problem, because when reprocessing occurs, those that cannot be processed will generate new issues to avoid repeated attempts to reprocess.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions