-
Notifications
You must be signed in to change notification settings - Fork 44.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(platform): Include all agent versions in Runs in Monitor #8752
feat(platform): Include all agent versions in Runs in Monitor #8752
Conversation
✅ Deploy Preview for auto-gpt-docs canceled.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small fix but big UX improvement. Thanks for picking this up :)
This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request. |
…-execution-on-the-latest-graph-version
Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly. |
✅ Deploy Preview for auto-gpt-docs-dev canceled.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! this is really cool!
…-execution-on-the-latest-graph-version
…d Graph Execution functions (#8939) This is a follow-up of #8752 There are several APIs and functions related to graph execution that are unused now. There is also confusion about the name of `GraphExecution` that exists in graph.py & execution.py. ### Changes 🏗️ * Renamed `GraphExecution` in `execution.py` to `GraphExecutionEntry`, this is only used as a queue entry for execution. * Removed unused `get_graph_execution` & `list_executions` in `execution.py`. * Removed `with_run` option on `get_graph` function in `graph.py`. * Removed `GraphMetaWithRuns` * Removed exposed functions only for testing. * Removed `executions` fields in Graph model. ### Checklist 📋 #### For code changes: - [ ] I have clearly listed my changes in the PR description - [ ] I have made a test plan - [ ] I have tested my changes according to the test plan: <!-- Put your test plan here: --> - [ ] ... <details> <summary>Example test plan</summary> - [ ] Create from scratch and execute an agent with at least 3 blocks - [ ] Import an agent from file upload, and confirm it executes correctly - [ ] Upload agent to marketplace - [ ] Import an agent from marketplace and confirm it executes correctly - [ ] Edit an agent from monitor, and confirm it executes correctly </details> #### For configuration changes: - [ ] `.env.example` is updated or already compatible with my changes - [ ] `docker-compose.yml` is updated or already compatible with my changes - [ ] I have included a list of my configuration changes in the PR description (under **Changes**) <details> <summary>Examples of configuration changes</summary> - Changing ports - Adding new services that need to communicate with each other - Secrets or environment variable changes - New or infrastructure changes such as databases </details> --------- Co-authored-by: Krzysztof Czerwinski <[email protected]>
The graph version is bumped on each save. While the agent version is changed, the past execution history is gone because the monitor page only shows the latest version's execution history.
Changes 🏗️
get_executions
on the backend that returns all executions of all graphs for a userExecutionMeta
toGraphExecution
for consistency with the backendFlowRun
type on the frontend and useGraphExecution
insteadChecklist 📋
For code changes:
Example test plan
For configuration changes:
.env.example
is updated or already compatible with my changesdocker-compose.yml
is updated or already compatible with my changesExamples of configuration changes