Fix maven v3 warn base64TypeError issue 16520 #16652
Merged
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
|
|
MarkvanOsch
changed the title
MarkvanOsch
changed the title
|
/azp run |
|
Azure Pipelines successfully started running 4 pipeline(s). |
max-zaytsev
approved these changes
Jul 29, 2022
alexander-smolyakov
approved these changes
Jul 29, 2022
kirill-ivlev
approved these changes
Jul 29, 2022
wojgasior
approved these changes
Jul 29, 2022
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.
Task name: Maven@3
Description: Not showing the incorrect warning when code coverage not enabled
##[warning]Fail to replace images source to base64TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type objectDocumentation changes required: N
Added unit tests: N
Attached related issue: #16520
Checklist: