[THRIFT-1863] [TBinaryProtocol readMessageBeginReturnName:type:sequenceID] returns incorrect message type - ASF JIRA

Voters

Watch issue

Watchers

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Minor
Resolution: Fixed
Affects Version/s: 0.9
Fix Version/s: None
Component/s: Cocoa - Library
Labels:
None

Patch Info:

Patch Available

Description

readMessageBeginReturnName in TBinaryProtocol uses the wrong variable to mask out the lower byte hence returning a wrong value for "type".

Attachments

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Manage Attachments

msgtype.patch
22/Feb/13 19:22
0.5 kB
Kevin Li

Activity

Comment

This comment will be Viewable by All Users Viewable by All Users

Cancel

People

Assignee:: Roger Meier

Reporter:: Kevin Li

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 22/Feb/13 19:21

Updated:: 25/Mar/13 08:40

Resolved:: 22/Mar/13 21:13

Agile

Slack

Issue deployment