Skip to content

Conversation

@EstelleDa
Copy link
Member

Remove unnecessary CSV files. Regardless of whether the scores and counts files are valid, users can successfully upload them at first. The validators check the files after uploading, so the response status codes are always 200 for both creating a score set and creating variants. We already have related validators and DataFrame tests, making these CSV files unnecessary.

However, a non-UTF8 file can still cause an issue. While users may be able to open it on their computer without problems, it will raise an error when uploading to MaveDB.

@EstelleDa EstelleDa requested a review from bencap March 4, 2025 08:05
@EstelleDa EstelleDa linked an issue Mar 4, 2025 that may be closed by this pull request
Copy link
Collaborator

@bencap bencap left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for looking into those errors Estelle. Eventually, we might want to support additional data encodings but it's probably pretty low priority.

@EstelleDa
Copy link
Member Author

My pleasure! We could keep it as a reminder and modify it in the future.

@EstelleDa EstelleDa merged commit 77cf4f7 into release-2025.1.1 Mar 5, 2025
5 checks passed
@EstelleDa EstelleDa deleted the estelle/debugUploadFilesUnicodeDecodeError branch March 5, 2025 04:17
@bencap bencap mentioned this pull request Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Get UnicodeDecodeError in uploading an invalid score file

3 participants