[MORAE] Multi-file support for linespan and code2amr slicing #652
Conversation
This file contains 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
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 PR fixed a small bug about making sure to only slice files that are in .py extensions.
It also added support for multi-file systems in both the linespan endpoint and the llm-assisted-codebase-to-pn-amr endpoint.
Some notes about the implementation, there is an assumption that zip files are walked over the same way each time and we are still only returning one AMR, to be consistent with the other code2amr endpoint. In the case we get multiple AMR's, (unpredictable LLM stuff) we will only return the AMR which has the most "states", which we use as a proxy for completeness. Default is the first amr, if say all amr's are empty.