exports v2 task support #933
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
February 22, 2023 16:11
…into ms/exports-v2-update
mnoszczak
approved these changes
Feb 22, 2023
kkim-labelbox
approved these changes
Feb 23, 2023
added 2 commits
February 22, 2023 19:15
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
yet another export/errors format...
note that it is hard to write a test case for the error condition because it only occurs when data row and project do not have a media type or we are exporting an unsupported annotation kind - which also isn't possible since all known kinds are supported.
I corrupted my local database to test. I also tested in staging on a project that has old data rows without mimetypes or project media types and it worked.
I also fixed a bug where one row ndjsons are treated as json. (dict instead of a list of dicts).