Stuck at "Parsing uploaded data"
I'm trying to import a small .jsonl file like the docs say, however I get stuck at "Parsing uploaded data" forever. The data is ok and it should pass schema validation. I originally tried with a .csv but no luck so I switched to jsonl but the result is the same.
I'm using mac with vscode and I've been able to import the data before, but no luck now whatsoever.
Any help? Thanks!
14 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
Yikes it seems we're not surfacing this error correctly. On our side i see this error
Does the file include any non-ascii characters?
yep! it includes spanish strings like "Córdoba", could that be an issue?
here's one of the JSONL lines for context:
{"externalId": 2, "isoId": "AR-C", "isoName": "Ciudad Autónoma de Buenos Aires", "name": "Ciudad Autónoma de Buenos Aires", "fullName": "Ciudad Autónoma de Buenos Aires"}it should be fine if it's utf-8 encoded. do you know how it's encoded?
BTW I have a lot of pending imports on my dashbaord. Could that be causing the other ones to never finish?
There's no way to cancel them either
yes i believe they try to execute in order. and we haven't built a way to cancel them for this case where they're hitting a misclassified error 😦 . they should automatically be canceled after being stuck for 24 hours
Yeah... I see the issue now. The first CSV I tried had an empty column, so that might have caused it to fail the first time
that could do it. darn
I guess I'll circle back on this in 24 hours. Thanks!
sorry about that. i'll fix this error for the next time it comes up, and we'll add cancelation
i'm struggling to reproduce the issue; how exactly does the CSV look? I tried starting the file with a newline, or with a comma, but those seem to work
hmm the OG CSV had an empty column and also two of them were coordinates, like -31.73857838
e.g.:
;lat;lng;externalId;name;provinceId;provinceName
;-31.3968471082745;-64.0598690981123;1401401002;La Floresta;14;Córdoba
;-32.8673131267475;-68.779539700913;5002802001;Bermejo;50;Mendoza
;-34.818755035018;-58.4233878258472;602801008;Malvinas Argentinas;6;Buenos Aires
;-34.844020734727;-58.3627535292892;602801009;Ministro Rivadavia;6;Buenos Aires
;-34.7973726678595;-58.3884529337359;602801001;Adrogué;6;Buenos Aires
;-34.8281717078487;-58.391033876775;602801002;Burzaco;6;Buenos Aires
;-34.7975588663845;-58.3352044170245;602801003;Claypole;6;Buenos Aires
;-34.8192915430555;-58.3418543079073;602801004;Don Orione;6;Buenos Aires
;-34.8883362582313;-58.3827874554173;602801005;Glew;6;Buenos AiresInteresting. I think the convex csv parser only supports comma delimiters, not semicolons. Maybe that's the issue 🤔
i believe all of your snapshot imports are unstuck now. sorry about the issue
Thanks a lot!