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

Python SDK: Missing parameter for "Dataset repository URL" in create_from_data() method #7415

Closed
2 tasks done
dpovision opened this issue Jan 31, 2024 · 4 comments
Closed
2 tasks done
Labels
enhancement New feature or request

Comments

@dpovision
Copy link

Actions before raising this issue

  • I searched the existing issues and did not find anything similar.
  • I read/searched the docs

Is your feature request related to a problem? Please describe.

I want to automatize the job task creation via high-level Python SDK API of CVAT and I can't find a parameter for the "Dataset repository URL" to create a backup storage.

Describe the solution you'd like

Please provide a possibility for the UI field "Dataset repository URL" in the high-level Python SDK API.

Describe alternatives you've considered

I tried to define the "Dataset repository URL" after task creation, but this seems also not possible via Python SDK.

Additional context

advanced_config

@dpovision dpovision added the enhancement New feature or request label Jan 31, 2024
@PMazarovich
Copy link
Contributor

That functionality was removed from CVAT

@dpovision
Copy link
Author

Thank you very much for your response.
Do you know the reason and how an automatic backup repository can be defined now or has it to be done manually?

@PMazarovich
Copy link
Contributor

PMazarovich commented Jan 31, 2024

From my understanding, this is impossible with native cvat features.
Here is the PR with explanation #6904
You can add your comment there and explain your usage, maybe that feature will be resurrected

@dpovision
Copy link
Author

dpovision commented Jan 31, 2024

Thank you very much again for your response. I left a comment in the other task #6904 and will close this task, since the feature is now not available anymore and therefore this parameter is technically spoken not missing anymore. But maybe we have luck and the feature is implemented again in future. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants