Task creation ignore manifest name in code
See original GitHub issueExpected Behaviour
When I add s3 storage with the specified name, it will be used on task creation with a chosen manifest name.
Update: remove the limit of manifest files in UI (5 currentlly)
Current Behaviour
Current implementation ignore settings and await manifest.jsonl
https://github.com/openvinotoolkit/cvat/blob/develop/cvat/apps/engine/task.py#L140
Without manifest.jsonl
file will raise Exception(‘A manifest file not found’)
https://github.com/openvinotoolkit/cvat/blob/develop/cvat/apps/engine/task.py#L241
And error “Unable to add manifest. The maximum number of files is 5.” in UI
Possible Solution
Would you please take the name from the chosen cloud storage settings? And remove limit
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Task creation ignore manifest name in code #3968 - GitHub
Expected Behaviour When I add s3 storage with the specified name, it will be used on task creation with a chosen manifest name....
Read more >Ignore a Manifest File During Deployment - Harness.io Docs
To have a Workflow ignore a resource file in a Service Manifests section, you add the comment # harness.io/skip-file-for-deploy to the ...
Read more >Manage manifest files - Android Developers
This page describes how manifest merging works and how you can apply merge preferences to resolve merge conflicts.
Read more >jar ignores my manifest - java - Stack Overflow
Also check that the last line of your manifest ends with a new line or carriage feed. I did not have ...
Read more >GenerateApplicationManifest Task - MSBuild - Microsoft Learn
If no name can be created, the task throws an error. ... If the task is generating a native manifest, this parameter is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It was implemented for some reason. Manifest is needed to describe the contents of the bucket and there was an opinion “one dataset - one bucket”. Maybe restrictions can be removed in the future. You can change restrictions here
If I understand you correctly, you need to look at here
@Marishka17 , could you please help and extend our documentation to make it clear?