bugfix: output expression incorrectly throws npe #4954
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
Codecov Report
@@ Coverage Diff @@
## develop #4954 +/- ##
=============================================
- Coverage 49.02% 49.02% -0.01%
- Complexity 4091 4092 +1
=============================================
Files 736 736
Lines 25818 25818
Branches 3184 3184
=============================================
- Hits 12657 12656 -1
- Misses 11815 11816 +1
Partials 1346 1346
|
funky-eyes
changed the title
funky-eyes
reviewed
Sep 24, 2022
There was a problem hiding this comment.
请在 https://github.com/seata/seata/tree/develop/changes 的中英两版develop.md进行此pr的登记,可参照其它人的登记方式,将pr和作者信息进行登记
|
已经登记 |
funky-eyes
added
type: bug
|
md文件里，贡献者名单里加一下自己的名字吧。 |
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.
Ⅰ. Describe what this PR did
output 表达式错误时，抛出期望的异常。而不是空指针
Ⅱ. Does this pull request fix one issue?
fixes #4948
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews