-
Notifications
You must be signed in to change notification settings - Fork 21
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
Fix incorrect state after indicator cancellation #346
Fix incorrect state after indicator cancellation #346
Conversation
Similar to #216 |
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.
For now, it is fine, but in the future, we need to find a better way to handle cancelation instead of repeating isCanceled check after each statement
How do you ensure that #314 gets closed? |
Kotlin coroutines support some smart cancelation mechanisms; transitioning to them in the future should help with this. |
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.
Before merging the PR, please answer this question.
@arksap2002
replay to #346 (comment) |
This PR is ready to merge |
@arksap2002 Do not forget to publish a new patch version of the |
The patch version changed due to fixes in the internal implementation of the `LLMWithFeedbackCycle.run` method.
6529d29
to
5c7a385
Compare
Published core module of version |
Description of changes made
isProcessStopped
method calls relocation due to long time methods processingTODOs
5.0.1
.Other notes
Closes #213 #314