fix: added llm based json parsing handling

[sauravpanda]

Summary

Added error handling and retry mechanism using llm for JSON parsing to handle potential failures.

Details

• Added new function 'extract_json_with_llm_retry' to handle JSON parsing with retry logic
• Modified 'review_pull_request' and 'generate_pull_request_desc' functions to use 'extract_json_with_llm_retry' for error handling
• Improved error resilience and user interaction by utilizing chat completion in case of JSON parsing failure
• Introduced 'total_usage' parameter for tracking usage throughout the process
• Refactored code for better error management and readability
• Updated pull request description generation to accommodate changes in error handling

✨ Generated with love by Kaizen ❤️

Original Description

None

[kaizen-bot]

Code Review

✅ All Clear: This PR is ready to merge! 👍

Potential Issues

[important] -> The except block in extract_json_with_llm_retry method is catching all exceptions, which may hide unexpected errors. It's better to handle specific exceptions or at least log the caught exception for debugging purposes.

Potential Solution:

Update the except block to handle specific exceptions or log the caught exception for debugging purposes.

parser.py | 7 - 18

request_for_change: True

Improvements

[important] -> The method extract_json_with_llm_retry does not have explicit comments or documentation describing its purpose, parameters, and return value, which may impact the code's maintainability and readability.

Potential Solution:

Add docstrings or comments to the extract_json_with_llm_retry method to explain its purpose, parameters, and return value.

parser.py | 6 - 12

request_for_change: True

✨ Generated with love by Kaizen ❤️

[cloudcodeai-nightly]

Code Review

✅ All Clear: This PR is ready to merge! 👍

Improvements

[important] -> Handle specific exceptions rather than a generic except clause

Potential Solution:

Instead of using a generic except clause, it is better to handle specific exceptions that may occur during JSON parsing or handling. This allows for better error reporting and handling. For example, you can catch specific exceptions like ValueError or JSONDecodeError and handle them accordingly.

kaizen/helpers/parser.py | 10 - 10

request_for_change: True

[important] -> Avoid catching all exceptions in the except clause

Potential Solution:

Catching all exceptions in the except clause can make it difficult to determine the cause of an error. It is better to catch only the specific exceptions that may occur during JSON parsing or handling. This allows for better error reporting and handling. Consider catching specific exceptions like ValueError or JSONDecodeError instead of using a generic except clause.

kaizen/helpers/parser.py | 13 - 13

request_for_change: True

✨ Generated with love by Kaizen ❤️