We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The condition will always be false, so the block will never be executed. Constant value:
protobuf/proto/text_decode.go
Line 22 in 5d5e8c0
Lines 33 to 35 in 5d5e8c0
Lines 51 to 59 in 5d5e8c0
protobuf/proto/text_encode.go
Line 23 in 5d5e8c0
Lines 54 to 70 in 5d5e8c0
protobuf/jsonpb/decode.go
Line 25 in 5d5e8c0
Lines 97 to 126 in 5d5e8c0
protobuf/jsonpb/encode.go
Line 26 in 5d5e8c0
Lines 97 to 108 in 5d5e8c0
Found by Linux Verification Center (portal.linuxtesting.ru) with SVACE. Author A. Voronin.
The text was updated successfully, but these errors were encountered:
The wrapTextUnmarshalV2 value is part of the Google-internal use of this package, and is not always false for them.
wrapTextUnmarshalV2
false
Since Google uses a duplicate of this code internally, there’s some things like this.
Sorry, something went wrong.
No branches or pull requests
Issue Description
The condition will always be false, so the block will never be executed.
Constant value:
protobuf/proto/text_decode.go
Line 22 in 5d5e8c0
Blocks IF:
protobuf/proto/text_decode.go
Lines 33 to 35 in 5d5e8c0
protobuf/proto/text_decode.go
Lines 51 to 59 in 5d5e8c0
And this case is in other file:
protobuf/proto/text_encode.go
Line 23 in 5d5e8c0
protobuf/proto/text_encode.go
Lines 54 to 70 in 5d5e8c0
Similar case is in other files:
protobuf/jsonpb/decode.go
Line 25 in 5d5e8c0
protobuf/jsonpb/decode.go
Lines 97 to 126 in 5d5e8c0
protobuf/jsonpb/encode.go
Line 26 in 5d5e8c0
protobuf/jsonpb/encode.go
Lines 97 to 108 in 5d5e8c0
Found by Linux Verification Center (portal.linuxtesting.ru) with SVACE.
Author A. Voronin.
The text was updated successfully, but these errors were encountered: