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

Re-uploading a saved recording does not modify the second file name #398

Closed
jan-law opened this issue Mar 22, 2022 · 5 comments · Fixed by #431
Closed

Re-uploading a saved recording does not modify the second file name #398

jan-law opened this issue Mar 22, 2022 · 5 comments · Fixed by #431
Assignees
Labels
bug Something isn't working needs-documentation

Comments

@jan-law
Copy link
Contributor

jan-law commented Mar 22, 2022

Behaviour occurs on the main branch as well as #397

To reproduce bug:

  1. Create a recording
  2. Archive the recording
  3. Download the recording you just archived
  4. Re-upload the downloaded recording
  5. The second file name is the same as the first one. Any "Delete" or "Edit Metadata" actions affect both recordings.

image

This alternative code path works fine - I'm assuming this is the intended behaviour:
Click the 'plus' icon and upload the same recording file twice, the second recording gets a number appended to it.
image

@jan-law jan-law added the bug Something isn't working label Mar 22, 2022
@andrewazores
Copy link
Member

This happens because re-uploading a recording into the archives puts it into a general, "unlabelled" archives subdirectory, rather than the one belonging to the selected target. If you repeat this procedure in #397, I think the per-target archives on the Recordings page should behave as expected, since it also no longer allows for recordings to be uploaded to the general "unlabelled" subdirectory from there, and the query it performs should only return results from the correct archive subdirectory as well. The new Archives page can still display these apparent duplicates however.

@andrewazores
Copy link
Member

Since #397 is merged this bug should not appear in the Recordings page archives tab, but it will still affect the new All Archives view (until #431).

@andrewazores
Copy link
Member

@dfitzmau @kucollin can we document this as a Known Issue for 2.1.0? It is a small display-only bug that affects the new Archives view.

@andrewazores andrewazores moved this to In Progress in 2.2.0 Release May 18, 2022
@dfitzmau
Copy link

Hi @andrewazores . Yes, we can document this. Just to confirm the issue still exists? I'm asking as two PRs exist related to this issue.

#437
#398

@andrewazores
Copy link
Member

@dfitzmau yes, the issue still exists. Those PRs have not been merged yet, so there won't be a fix in a product version until 2.2.0 later this year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-documentation
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants