Conversation
…cription in regression test nodes
… in bug regression handling
…y and completeness
…hes when applicable
…max refined query loops
…ginal query, and aggregated context sections
…s include line numbers
…_regression_subgraph.py
…ieval_subgraph.py and file_operation.py
…ug_get_regression_tests_subgraph.py; add handling for empty selected regression tests in run_regression_tests_subgraph_node.py
…for clarity, update state management, and enhance logging for tested patches
…cted_regression_tests' for clarity in multiple files
…ss_regression_test_patch_check_result_node.py and get_pass_regression_test_patch_state.py
…annotations for clarity and consistency, replacing Dict with IssueNotVerifiedBugState and TypedDict with BaseModel
…patches as passed if no new failures are introduced, improving clarity in test result evaluation
…ance query specificity and improve data retrieval consistency
…ate related logic for improved test result evaluation
…or handling and reset git repository state
…mprove error management for recursion limits
… improved handling
…date state management
…tput structure and improve message clarity
… update assertion checks
…g for unsupported files
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request introduces support for regression test execution and tracking throughout the issue handling workflow, enhances file type support for knowledge graph building, and improves code clarity and maintainability. The most significant changes are grouped below:
Regression Test Support and API Changes:
run_regression_testandpassed_regression_testfields to theIssueRequest,IssueResponse, and related service/data flow, enabling the system to run and report regression test results as part of issue processing. This includes updates to function signatures, request/response models, and state dictionaries. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]Knowledge Graph Improvements:
.markdownas a supported text file extension. This ensures only relevant files are processed, reducing unnecessary computation and log noise. [1] [2] [3] [4]Git Repository Handling:
GitRepositoryby centralizing patch application into a newapply_patchmethod, and ensured repository reset occurs after certain operations to maintain a clean state. [1] [2]Bug Fix Verification Subgraph and Node Updates:
Other Minor Improvements:
IssueRequestfor improved patch selection.These changes collectively improve the system's robustness, test coverage, and maintainability.