Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug in filebrowser: Copy/paste of 2 files leads to content swap #12237

Open
jhgoebbert opened this issue Mar 19, 2022 · 1 comment
Open

bug in filebrowser: Copy/paste of 2 files leads to content swap #12237

jhgoebbert opened this issue Mar 19, 2022 · 1 comment

Comments

@jhgoebbert
Copy link

Description

If one has two files called test-Copy.file and test.file in a directory and uses the context menu's Copy and Paste to copy them to another directory

  1. the content of the files is swapped

grafik
grafik

  1. test-Copy.file gets renamed to test-Copy1.file

Reproduce

  1. create two files called test.file and test-Copy.file
  2. give both a different content
  3. select both in the JupyterLab filebrowser
  4. use the context menu of the JupyterLab filebowser to click "Copy"
  5. open a different directory
  6. use the context menu of the JupyterLab filebowser to click "Paste"

The filecontent will be swapped and the filename test-Copy.file will be test-Copy1.file

Expected behavior

file-content is not swapped and file-names are not changed

Context

  • Operating System and version: Windows 10
  • Browser and version: Firefox 98.01
  • JupyterLab version: 3.2.1 and 3.3.2
@jhgoebbert jhgoebbert added the bug label Mar 19, 2022
@jupyterlab-probot jupyterlab-probot bot added the status:Needs Triage Applied to new issues that need triage label Mar 19, 2022
@JasonWeill
Copy link
Contributor

In #12236, test-Copy.file appears to be getting renamed to test.file. In this example, test.file appears to be getting renamed to test-Copy1.file.

Not sure if this represents distinct work from #12236. The "rename on copy/paste" logic might need to be rewritten or removed to address both of these bugs.

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

No branches or pull requests

2 participants