Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • funkwhale funkwhale
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 409
    • Issues 409
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 19
    • Merge requests 19
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • funkwhalefunkwhale
  • funkwhalefunkwhale
  • Issues
  • #1349
Closed
Open
Issue created Mar 02, 2021 by gammelalf@gammelalf

/api/v1/uploads/{uuid} gives 404 on skipped upload

I'm trying to write a python wrapper for the api and automate uploading with it.

When I upload the same track twice, the uuid returned by the second upload request leads into nowhere.

I have checked the db using the django admin interface:

  • The second upload exists
  • Its uuid was returned correctly
  • When I change its import status to Finished instead of Skipped, it works normally

Steps to reproduce

  1. Upload a song twice, so the second upload gets marked as skipped
  2. Try to get the second upload via /api/v1/uploads/{uuid} (it returns 404)

Bonus Steps

  1. Edit the import status of the second upload in the db and set it to Finished
  2. Try again (now it works)

What happens?

It returns a 404

What is expected?

It should return the same data which it would, if the upload hadn't been skipped.

Context

Tried it on two different funkwhale instances, both version 1.0.1+git.68bc76bc.

Edited Apr 09, 2021 by funkwhale-bot
Assignee
Assign to
Time tracking