Closed nleroy917 closed 3 days ago
75K is very huge PEP. I think PEPhub server can fail if you will try to open this pep using peppy. I would say, let's not do this. At this point max pep should be less then 10K
Yeah I agree. I say we just catch the 413 and notify the user there's a max file size limit.
I agree that 75k is probably outside the scope of what we were thinking.
I'm assuming this was embeddings? Maybe we need a separate service with database of embeddings?
It was actually GEO_GSM_complete
It was actually
GEO_GSM_complete
This file is more than 300 MB, it's too huge + too many columns.
In the future, I think it will be possible to store such a big files if we will develop new way for getting samples, but for right now it is impossible
I'm working with a group that wants to hold a large table, maybe on the scale of 10,000 records.
He pasted 2000 records into the table, and the javascript could handle it, but when he clicked 'Save' it said "Unknown Error Occurred".
with 1000 rows, it worked.
Can we clarify this?
This issue was solved in pephub 0.11.9
I was trying to upload a very large sample table. It had >75,000 samples, with 1875(I think?) attributes per sample. The file was ~325 megabytes.
PEPhub responded with this toast message:
Two things I bring up:
413
and render a more user-friendly toast message?