-
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
chore(platform):Refactor GraphExecution naming clash and remove unused Graph Execution functions #8939
Conversation
…d Graph Execution functions
✅ Deploy Preview for auto-gpt-docs-dev canceled.
|
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
✅ 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.
Good cleanup 😊
Co-authored-by: Krzysztof Czerwinski <[email protected]>
Co-authored-by: Krzysztof Czerwinski <[email protected]>
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 🏗️
GraphExecution
inexecution.py
toGraphExecutionEntry
, this is only used as a queue entry for execution.get_graph_execution
&list_executions
inexecution.py
.with_run
option onget_graph
function ingraph.py
.GraphMetaWithRuns
executions
fields in Graph model.Checklist 📋
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