todo: separate jvm specific coverage_enhancer agent (jvm_coverage_enhancer) #1021
Conversation
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
DavidKorczynski
suggested changes
Apr 29, 2025
|
Regarding the lints, please note that this project uses 2-space indentation for Python code, not 4-space. |
|
hii @arthurscchan / @DavidKorczynski i had done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 is based on todo listed in enhancer.py which separates the logic of jvm coverage via JvmFixingBuilder in a separate agent .
cc : @DavidKorczynski / @DonggeLiu please take a look on this pr on your free time , thank you!