-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
There is a bug in the break_cycle logic in CodeReview #387
Comments
thank you! you are right. could u please make a pr on it? |
"Okay, my solution above still has some issues. I'll think about how to fix it." |
I've found the issue. Here's a better solution: |
Based on the previous issue, another problem has been identified: |
I have an idea that might solve this problem. We can categorize the dialogue conclusion markers in the prompt into two types. One type needs to be included in the context to provide information for downstream use, such as " PowerPoint" in DemandAnalysis. The other type is just a marker for ending, such as " Finished" in CodeReviewComment. I suggest changing " Finished" in CodeReviewComment to " Finished". |
composed_phase.py
According to the prompt, " Finished" is only returned during the CodeReviewComment stage, and the conclusion of this stage will be stored in chat_env.env_dict['review_comments']. There seems to be a bug in the current code logic. I believe the correct code should be as follows:
The text was updated successfully, but these errors were encountered: