Good working script processing api, now returns "markdown": "NO_CONTENT_HERE" #282

Closed
opened 2026-02-16 00:17:22 -05:00 by yindo · 2 comments
Owner

Originally created by @weisisheng on GitHub (Sep 28, 2024).

Describe the bug
Using AWS lambda / axios with a function that has been in dev for the last few months. Tried running otday, ingesting multiple example pdfs, and the error returns "NO CONTENT HERE"

Files
https://hiring-report-public-files.s3.amazonaws.com/CSR_BioRender.pdf

It's called "misc-text.pdf" on the llamaparse console since I am sending it to /tmp file first from S3 before hitting the endpoint.

Job ID
If you have it, please provide the ID of the job you ran.
1eb1b8e0-b354-430c-bad6-3568fea0bc85

Screenshots

results from aws step functions / lamba

https://hiring-report-public-files.s3.amazonaws.com/Screenshot+from+2024-09-29+10-40-08.png

Options
Fast, no other instructions.

Additional context
Add any additional context about the problem here.

Originally created by @weisisheng on GitHub (Sep 28, 2024). **Describe the bug** Using AWS lambda / axios with a function that has been in dev for the last few months. Tried running otday, ingesting multiple example pdfs, and the error returns "NO CONTENT HERE" **Files** https://hiring-report-public-files.s3.amazonaws.com/CSR_BioRender.pdf It's called "misc-text.pdf" on the llamaparse console since I am sending it to /tmp file first from S3 before hitting the endpoint. **Job ID** If you have it, please provide the ID of the job you ran. 1eb1b8e0-b354-430c-bad6-3568fea0bc85 **Screenshots** # results from aws step functions / lamba https://hiring-report-public-files.s3.amazonaws.com/Screenshot+from+2024-09-29+10-40-08.png **Options** Fast, no other instructions. **Additional context** Add any additional context about the problem here.
yindo added the bug label 2026-02-16 00:17:22 -05:00
yindo closed this issue 2026-02-16 00:17:22 -05:00
Author
Owner

@weisisheng commented on GitHub (Sep 28, 2024):

Nah I am sure i don't. Stop with the phishing attacks, punk.

Noticed there is an error referencing the url in this documentation (two backslashes):

"https://api.cloud.llamaindex.ai//api/v1/parsing/upload"

Found here: https://docs.cloud.llamaindex.ai/API/upload-file-api-v-1-parsing-upload-post

***To the community: how do I report bad actors trying to corrupt the github platform? Edit: reported and blocked.

@weisisheng commented on GitHub (Sep 28, 2024): Nah I am sure i don't. Stop with the phishing attacks, punk. Noticed there is an error referencing the url in this documentation (two backslashes): "https://api.cloud.llamaindex.ai//api/v1/parsing/upload" Found here: https://docs.cloud.llamaindex.ai/API/upload-file-api-v-1-parsing-upload-post ***To the community: how do I report bad actors trying to corrupt the github platform? Edit: reported and blocked.
Author
Owner

@weisisheng commented on GitHub (Sep 29, 2024):

Closing this for now, seems the files are being corrupted further upstream during s3 posting process.

@weisisheng commented on GitHub (Sep 29, 2024): Closing this for now, seems the files are being corrupted further upstream during s3 posting process.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_cloud_services#282