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

[PR #170] [MERGED] WorkflowService #304

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

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama_deploy/pull/170
Author: @logan-markewich
Created: 8/8/2024
Status: ✅ Merged
Merged: 8/15/2024
Merged by: @logan-markewich

Base: v0.1.0 ← Head: logan/initial_workflows

📝 Commits (9)

📊 Changes

11 files changed (+1103 additions, -387 deletions)

View changed files

➕ examples/workflow_local_single.py (+43 -0)
➕ examples/workflow_server.py (+70 -0)
📝 llama_agents/__init__.py (+4 -0)
📝 llama_agents/launchers/local.py (+8 -4)
📝 llama_agents/orchestrators/__init__.py (+2 -0)
➕ llama_agents/orchestrators/simple.py (+73 -0)
📝 llama_agents/services/__init__.py (+2 -0)
➕ llama_agents/services/workflow.py (+346 -0)
📝 poetry.lock (+471 -382)
📝 pyproject.toml (+1 -1)
➕ tests/services/test_workflow_service.py (+83 -0)

📄 Description

This PR introduces a workflow service, for deploying workflows as services

It makes a few key assumptions

  • workflows are separated from their state
  • the state is passed in when running the service
  • the state of the workflow (i.e. the context) is currently pickled
    • we could avoid pickles if we ensure that the context can only hold basic serializable objects
    • currently I try to add some minor security by using salted hashes on the pickle string. Still not great

🔄 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/170 **Author:** [@logan-markewich](https://github.com/logan-markewich) **Created:** 8/8/2024 **Status:** ✅ Merged **Merged:** 8/15/2024 **Merged by:** [@logan-markewich](https://github.com/logan-markewich) **Base:** `v0.1.0` ← **Head:** `logan/initial_workflows` --- ### 📝 Commits (9) - [`051ccf1`](https://github.com/run-llama/llama_deploy/commit/051ccf1003ad14a338989a684c9ad779e57e51c4) wip - [`e61d099`](https://github.com/run-llama/llama_deploy/commit/e61d099bc6699fb7a03f7da3c5ae2d3adff7b750) bump - [`25a7fe4`](https://github.com/run-llama/llama_deploy/commit/25a7fe401895031a853d9c65fa45065a96306f07) passing test - [`cb48960`](https://github.com/run-llama/llama_deploy/commit/cb48960c511aa59292c1f81a95cdb4d6fe4d79c3) use PrivateAttr from pydantic v2 - [`d195d37`](https://github.com/run-llama/llama_deploy/commit/d195d37eb82e6cd2434f4bda7f4ebc403535af62) remove redundant workflow run - [`7ff1b8d`](https://github.com/run-llama/llama_deploy/commit/7ff1b8dbe5c6c165f48f9311c432ef85391b2609) wip simple orchestrator - [`ded2e7e`](https://github.com/run-llama/llama_deploy/commit/ded2e7e6ee2bea6149e5df418ea2027f469f24cf) Update llama_agents/services/workflow.py - [`a35ea9b`](https://github.com/run-llama/llama_deploy/commit/a35ea9bac448c330217c428b57ef1c6562359ecb) fix lock - [`ef4acfc`](https://github.com/run-llama/llama_deploy/commit/ef4acfc2af2a6f2fb6b43fe923a999d9f94c819f) initial examples ### 📊 Changes **11 files changed** (+1103 additions, -387 deletions) <details> <summary>View changed files</summary> ➕ `examples/workflow_local_single.py` (+43 -0) ➕ `examples/workflow_server.py` (+70 -0) 📝 `llama_agents/__init__.py` (+4 -0) 📝 `llama_agents/launchers/local.py` (+8 -4) 📝 `llama_agents/orchestrators/__init__.py` (+2 -0) ➕ `llama_agents/orchestrators/simple.py` (+73 -0) 📝 `llama_agents/services/__init__.py` (+2 -0) ➕ `llama_agents/services/workflow.py` (+346 -0) 📝 `poetry.lock` (+471 -382) 📝 `pyproject.toml` (+1 -1) ➕ `tests/services/test_workflow_service.py` (+83 -0) </details> ### 📄 Description This PR introduces a workflow service, for deploying workflows as services It makes a few key assumptions - workflows are separated from their state - the state is passed in when running the service - the state of the workflow (i.e. the context) is currently **pickled** - we could avoid pickles if we ensure that the context can only hold basic serializable objects - currently I try to add some minor security by using salted hashes on the pickle string. Still not great --- <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:16:49 -05:00
yindo closed this issue 2026-02-16 01:16:49 -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#304
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?