You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has been observed for the accession upload but may also be happening in other uploads: Sometimes the Excel parser cannot determine the end of the "data zone" in the Excel file and continues parsing to the end of the Excel file, parsing 100,000s of rows and of course timing out in the process. We need to manually check the end of the parsing, such as checking for empty values.
It is not clear what causes this to happen, I think it is when columns or copied around potentially it will set the "data zone" to the entire column length.
The text was updated successfully, but these errors were encountered:
I did check the example file from Lukas and it does have a lot of "blank" rows (rows with no data, but are still included in the Excel file, likely because they have formatting information). I don't think it is the file parser that is causing the slow upload - it will stop parsing the file after 5 empty rows. The slow part seems to be the Fuzzy Search when uploading accessions.
This has been observed for the accession upload but may also be happening in other uploads: Sometimes the Excel parser cannot determine the end of the "data zone" in the Excel file and continues parsing to the end of the Excel file, parsing 100,000s of rows and of course timing out in the process. We need to manually check the end of the parsing, such as checking for empty values.
It is not clear what causes this to happen, I think it is when columns or copied around potentially it will set the "data zone" to the entire column length.
The text was updated successfully, but these errors were encountered: