run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-07-18 15:54:38 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

[PR #929] [MERGED] Handle reasoning field conflict #966

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

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama_cloud_services/pull/929
Author: @adrianlyjak
Created: 9/21/2025
Status: ✅ Merged
Merged: 9/22/2025
Merged by: @adrianlyjak

Base: main ← Head: adrian/extraction-metadata-bug

📝 Commits (2)

  • f20cf5c Handle reasoning field conflict
  • b22bb1b update version to 0.6.69

📊 Changes

5 files changed (+61 additions, -11 deletions)

View changed files

📝 py/llama_cloud_services/beta/agent_data/schema.py (+9 -7)
📝 py/llama_parse/pyproject.toml (+2 -2)
📝 py/pyproject.toml (+1 -1)
📝 py/unit_tests/beta/agent/test_agent_data_schema.py (+48 -0)
📝 py/uv.lock (+1 -1)

📄 Description

Handles the scenario where "reasoning" exists in the user schema

🔄 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/929 **Author:** [@adrianlyjak](https://github.com/adrianlyjak) **Created:** 9/21/2025 **Status:** ✅ Merged **Merged:** 9/22/2025 **Merged by:** [@adrianlyjak](https://github.com/adrianlyjak) **Base:** `main` ← **Head:** `adrian/extraction-metadata-bug` --- ### 📝 Commits (2) - [`f20cf5c`](https://github.com/run-llama/llama_cloud_services/commit/f20cf5c8b967321f54f17535b3ce3f437e6478f8) Handle reasoning field conflict - [`b22bb1b`](https://github.com/run-llama/llama_cloud_services/commit/b22bb1b4b76bf904d227003e6f88a4d24d4b23c3) update version to 0.6.69 ### 📊 Changes **5 files changed** (+61 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `py/llama_cloud_services/beta/agent_data/schema.py` (+9 -7) 📝 `py/llama_parse/pyproject.toml` (+2 -2) 📝 `py/pyproject.toml` (+1 -1) 📝 `py/unit_tests/beta/agent/test_agent_data_schema.py` (+48 -0) 📝 `py/uv.lock` (+1 -1) </details> ### 📄 Description Handles the scenario where "reasoning" exists in the user schema --- <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:19:41 -05:00
yindo closed this issue 2026-02-16 00:19:41 -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#966
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?