Skip to content

unwanted behavior when using copy command #60

@nconrad

Description

@nconrad

Creating a ticket over here for tracking purposes. This shouldn't be an issue in the UI.

Issue:
Calling Workspace.copy, move=true, in parallel–before the server responds to the first request–may result in data "disappearing" from Workspace.ls.

The server also seems to think the file(s?) still exist.

Example:
I can no longer create a folder called /devuser@patricbrc.org/home/Escherichia testing6

The error is:

mkdir /disks/p3/workspace/P3WSDB/devuser@patricbrc.org/home//Escherichia testing6: File exists

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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