-
Notifications
You must be signed in to change notification settings - Fork 5.4k
ref: state - 2 #4229
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
ref: state - 2 #4229
Conversation
@codex review this deeply |
Codex Review: Didn't find any major issues. Breezy! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting |
There is a known bug with the sync abort. Fix in progress |
} | ||
|
||
#[tokio::test] | ||
async fn abort_regular_task_emits_turn_aborted_only() { |
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.
have you considered making these integration style tests? We can simulate never ending task by having server return tool calls forever.
also maybe movign them out of codex.rs
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.
Yes I want to add full integration tests around this but still in todo
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.
Approving to unblock. Independently from my comments this is a step in the right direction.
@codex fix the CLI |
Summary
Testing
|
Extracting tasks in a module and start abstraction behind a Trait (more to come on this but each task will be tackled in a dedicated PR)
The goal was to drop the ActiveTask and to have a (potentially) set of tasks during each turn