Re: Crazy TBinaryProtocol

Andre', Another suggestion: these other clients, I presume, are in other languages? Could you take that string, and write a cmdline program that demarshals it in one of the other languages that work? Just to verify that indeed it's just a Python-only problem? On Thu, Jan 11, 2018 at 12:42 PM,

Re: Crazy TBinaryProtocol

Andre', (1) The message is generated in which language? Python? (2) Can you supply the IDL for the message payload and message itself? On Thu, Jan 11, 2018 at 10:35 AM, André Lemos wrote: > On Thu, Jan 11, 2018 at 5:32 PM, Kevin Clark > wrote: > > >

Turning off Context parameter generation in Go for 0.11.0

Hi, I noticed that the Go generator for 0.11.0 automatically generates a context parameter for each function it generates. I was wondering if there was an option to turn this off as I don't currently see much of a need for passing down context in my own use-case and it causes a lot of breakage

Re: Crazy TBinaryProtocol

On Thu, Jan 11, 2018 at 5:32 PM, Kevin Clark wrote: > On Thu, Jan 11, 2018 at 8:41 AM André Lemos wrote: > > > On Thu, Jan 11, 2018 at 4:34 PM, Kevin Clark > > wrote: > > > > > On Thu, Jan 11, 2018 at 8:19 AM André Lemos

Re: Crazy TBinaryProtocol

On Thu, Jan 11, 2018 at 8:41 AM André Lemos wrote: > On Thu, Jan 11, 2018 at 4:34 PM, Kevin Clark > wrote: > > > On Thu, Jan 11, 2018 at 8:19 AM André Lemos wrote: > > > > > On Thu, Jan 11, 2018 at 4:13 PM, Kevin Clark

Re: Crazy TBinaryProtocol

I've looked it up, but the C++ client does not use Framed messages, and that is working. On Thu, Jan 11, 2018 at 5:20 PM, Ben Craig wrote: > This kind of issue usually arises when one side is using a framed message > and the other side is not. > > On Thu, Jan 11, 2018 at

Re: Crazy TBinaryProtocol

This kind of issue usually arises when one side is using a framed message and the other side is not. On Thu, Jan 11, 2018 at 10:40 AM, André Lemos wrote: > On Thu, Jan 11, 2018 at 4:34 PM, Kevin Clark > wrote: > > > On Thu, Jan 11, 2018 at 8:19 AM André

Re: Crazy TBinaryProtocol

Hi James, Not quite sure I follow you. I am just looking to the payload of a TBinaryProtocol message. Should there be something else? There are other clients that digest this message correctly, so I am sure the issue is on my end. On Thu, Jan 11, 2018 at 4:34 PM, James King

Re: Crazy TBinaryProtocol

On Thu, Jan 11, 2018 at 8:19 AM André Lemos wrote: > On Thu, Jan 11, 2018 at 4:13 PM, Kevin Clark > wrote: > > > On Thu, Jan 11, 2018 at 7:40 AM André Lemos wrote: > > > > > Hi, > > > > > > > > > When parsing through a TBinaryProtocol,

Re: Crazy TBinaryProtocol

Hi, suggest you start by looking at the binary protocol documentation at: https://github.com/apache/thrift/blob/master/doc/specs/thrift-binary-protocol.md See if you are getting a complete message or not, that will help you narrow the issue down to the sender or the receiver? If you are supposed

Re: Crazy TBinaryProtocol

On Thu, Jan 11, 2018 at 4:13 PM, Kevin Clark wrote: > On Thu, Jan 11, 2018 at 7:40 AM André Lemos wrote: > > > Hi, > > > > > > When parsing through a TBinaryProtocol, trying to get the > readMessageBegin, > > readI32, returns 16777216, which will raise

Re: Crazy TBinaryProtocol

On Thu, Jan 11, 2018 at 7:40 AM André Lemos wrote: > Hi, > > > When parsing through a TBinaryProtocol, trying to get the readMessageBegin, > readI32, returns 16777216, which will raise an EOFError, because it's just > a too big of a value. If I use something like 25, I do get

Crazy TBinaryProtocol

Hi, When parsing through a TBinaryProtocol, trying to get the readMessageBegin, readI32, returns 16777216, which will raise an EOFError, because it's just a too big of a value. If I use something like 25, I do get something pretty closer to what I am trying to get, although I still get the