run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-07-01 21:44:37 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

[PR #1081] [MERGED] Use error description in invalid extraction error #1065

New Issue
Closed
opened 2026-02-16 00:20:01 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 00:20:01 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama_cloud_services/pull/1081
Author: @adrianlyjak
Created: 1/18/2026
Status: ✅ Merged
Merged: 1/18/2026
Merged by: @adrianlyjak

Base: main ← Head: claude/refactor-invalid-extraction-error-j6fJs

📝 Commits (2)

  • 3b1e2b4 fix: display extraction job error in InvalidExtractionData exception
  • 49fbad6 Create three-yaks-beg.md

📊 Changes

3 files changed (+74 additions, -4 deletions)

View changed files

➕ .changeset/three-yaks-beg.md (+5 -0)
📝 py/llama_cloud_services/beta/agent_data/schema.py (+27 -4)
📝 py/unit_tests/beta/agent/test_agent_data_schema.py (+42 -0)

📄 Description

Refactored InvalidExtractionData to read the error field from ExtractRun and prominently display it in the exception message. The job-level error is now stored in the extraction_error attribute and included in the invalid_item's metadata as job_error.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/llama_cloud_services/pull/1081 **Author:** [@adrianlyjak](https://github.com/adrianlyjak) **Created:** 1/18/2026 **Status:** ✅ Merged **Merged:** 1/18/2026 **Merged by:** [@adrianlyjak](https://github.com/adrianlyjak) **Base:** `main` ← **Head:** `claude/refactor-invalid-extraction-error-j6fJs` --- ### 📝 Commits (2) - [`3b1e2b4`](https://github.com/run-llama/llama_cloud_services/commit/3b1e2b4524f8a026c28941504e98b848ac8069aa) fix: display extraction job error in InvalidExtractionData exception - [`49fbad6`](https://github.com/run-llama/llama_cloud_services/commit/49fbad6fe420ea41a0f7d2530cfaea6ca48a1c56) Create three-yaks-beg.md ### 📊 Changes **3 files changed** (+74 additions, -4 deletions) <details> <summary>View changed files</summary> ➕ `.changeset/three-yaks-beg.md` (+5 -0) 📝 `py/llama_cloud_services/beta/agent_data/schema.py` (+27 -4) 📝 `py/unit_tests/beta/agent/test_agent_data_schema.py` (+42 -0) </details> ### 📄 Description Refactored InvalidExtractionData to read the `error` field from ExtractRun and prominently display it in the exception message. The job-level error is now stored in the `extraction_error` attribute and included in the invalid_item's metadata as `job_error`. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 00:20:01 -05:00
yindo closed this issue 2026-02-16 00:20:01 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
LlamaCloud
LlamaExtract
LlamaParse
bug
client
complex layout
documentation
duplicate
enhancement
figure
font
header footer
help wanted
ocr
parser
pdf_debug
pdf_debug
pull-request
Mirrored from GitHub Pull Request
 python-lib
question
server_issue
server_issue
ui
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_cloud_services#1065
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?