-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Regarding the issue of using CVAT API to backup task return value 202 #7878
Comments
@youth123-c the download apis are normally async 202 means task submitted. it is actually a success response you will find the backup file on some other API in UI the javascrip generally take care of this, I don't know which is the second API in case of CVAT but I based of network observation you have to keep hitting same request until you get 201 with param action='download'. even if you put your request in while with this param I don't thik it will work here one example from cvat_sdk import make_client, models
with make_client(host=CVAT_HOST, credentials=(CVAT_USER, CVAT_PASS)) as client:
task_meta = client.tasks.retrieve(download_task_id)
task_meta.export_dataset(format_name="CVAT for images 1.1", filename=local_path) |
Thank you very much for your help, I will try it using cvat sdk |
Did you sort out how to work with backup API? |
I used cavt sdk to download the task, but I found that the export_dataset method downloads image and annotation. If I only want to download annotation, I should use that method? |
Actions before raising this issue
Steps to Reproduce
Expected Behavior
When I have a large task_id list, for example, the length is 300, 30 task_id backups will fail, and the backup interface return value is 202.
Possible Solution
I added retry to the backup interface and tried 5 times with an interval of 8 seconds each time. When I ran the script recently, I found that the same batch of task_ids failed each time.
Context
I want to solve this 202 return value problem and back up all the data when I do batch backup.
Environment
The text was updated successfully, but these errors were encountered: