Skip to content

Existing "run_records" folder should not block run startΒ #172

@corrodis

Description

@corrodis

I encountered a problem where the previous run likely crashed after the "run_records" folder was created, but the run had not yet been written to the database. Since we are getting the run numbers from a database, the next run has the same run number, but a run_records folder already exists. This essentially locks the system without manual intervention.

I think we might want to disable the check in:

subdir.split("/")[-1]

Or keep the test, but if a folder is already there, rename the old folder or alike?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    πŸ•‘ Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions