Skip to content

possible data loss from unexpected confirmation prompt #21

@username-not-taken

Description

@username-not-taken

i don't really know what happened here. first i thought that there was a stream with the exact same name but this should not be possible since there is a timestamp too and it should keep the names unique. all i know is that there was an unexpected confirmation prompt that i didn't know about for many days. would appreciate it a lot if this could be fixed somehow by maybe using another name automatically if the file exist instead of stopping the whole thing at an prompt that requires manual input
prompt

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions