run-llama/llama_deploy
1
0
Fork 0
mirror of https://github.com/run-llama/llama_deploy.git synced 2026-08-25 10:39:36 -04:00
Code Issues 37 Packages Projects Releases 10 Wiki Activity

[PR #407] [MERGED] fix: apiserver doesn't set session id when creating a task #442

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

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama_deploy/pull/407
Author: @masci
Created: 12/16/2024
Status: ✅ Merged
Merged: 12/16/2024
Merged by: @masci

Base: main ← Head: massi/fix-apiserver

📝 Commits (2)

  • 8381f17 fix: apiserver doesn't set session id when creating a task
  • 4ab7cdd make the assert more informative

📊 Changes

3 files changed (+8 additions, -17 deletions)

View changed files

📝 e2e_tests/apiserver/test_streaming.py (+1 -1)
📝 e2e_tests/basic_streaming/test_run_client.py (+6 -16)
📝 llama_deploy/apiserver/routers/deployments.py (+1 -0)

📄 Description

Probably a leftover of the migration to the new Client, not sure why e2e didn't catch it earlier

🔄 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_deploy/pull/407 **Author:** [@masci](https://github.com/masci) **Created:** 12/16/2024 **Status:** ✅ Merged **Merged:** 12/16/2024 **Merged by:** [@masci](https://github.com/masci) **Base:** `main` ← **Head:** `massi/fix-apiserver` --- ### 📝 Commits (2) - [`8381f17`](https://github.com/run-llama/llama_deploy/commit/8381f179a07707482d5faf21c93cfa3f5688d849) fix: apiserver doesn't set session id when creating a task - [`4ab7cdd`](https://github.com/run-llama/llama_deploy/commit/4ab7cddb44ef157c829fc2c25d0d949d4a40150d) make the assert more informative ### 📊 Changes **3 files changed** (+8 additions, -17 deletions) <details> <summary>View changed files</summary> 📝 `e2e_tests/apiserver/test_streaming.py` (+1 -1) 📝 `e2e_tests/basic_streaming/test_run_client.py` (+6 -16) 📝 `llama_deploy/apiserver/routers/deployments.py` (+1 -0) </details> ### 📄 Description Probably a leftover of the migration to the new Client, not sure why e2e didn't catch it earlier --- <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 01:17:22 -05:00
yindo closed this issue 2026-02-16 01:17:22 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0
P1
P2
bug
documentation
documentation
enhancement
example
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
topic:CLI
topic:SDK
topic:SDK
topic:SDK
topic:apiserver
topic:control_plane
topic:message_queues
wontfix
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_deploy#442
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?