fix: move class-level attributes to instance-level in Conversation class #418
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #417
Why:
Class-level attributes persisted state between sessions. Making them instance-level ensures each session starts fresh.
What:
Moved
_thread
,_should_stop
,_conversation_id
, and_last_interrupt_id
from class-level to instance-level within the init method.Note: This pull request is a proof of concept, demonstrating how moving class-level attributes to instance-level resolves the session interference issue. I understand this can’t be merged directly due to the code generation process.