-
Couldn't load subscription status.
- Fork 22
[FIX] log final explanation #668
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
Changes from all commits
d3fed4e
19cd223
370e4e6
60df8f6
90eaf90
aefe030
c4e15cf
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1158,7 +1158,6 @@ def find_and_process_best_optimization( | |
| original_helper_code, | ||
| code_context, | ||
| ) | ||
| self.log_successful_optimization(explanation, generated_tests, exp_type) | ||
| return best_optimization | ||
|
|
||
| def process_review( | ||
|
|
@@ -1232,10 +1231,9 @@ def process_review( | |
| file_path=explanation.file_path, | ||
| benchmark_details=explanation.benchmark_details, | ||
| ) | ||
| self.log_successful_optimization(new_explanation, generated_tests, exp_type) | ||
|
|
||
| best_optimization.candidate.explanation = new_explanation | ||
|
|
||
| console.print(Panel(new_explanation_raw_str, title="Best Candidate Explanation", border_style="blue")) | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. print should remain there @mohammedahmed18 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @aseembits93 1234| self.log_successful_optimization(new_explanation, generated_tests, exp_type)There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. sounds good @mohammedahmed18 |
||
| best_optimization.explanation_v2 = new_explanation.explanation_message() | ||
|
|
||
| data = { | ||
| "original_code": original_code_combined, | ||
|
|
||
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.
Q: why we arent having old explanation and new explanation as sep field here?
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.
i would propose to keep it frozen. we can instantiate a new candidate with the new explanation. we don't want to corrupt the existing data we have.