hft | real high-frequency-trading system based on c | Cryptocurrency library

The Strategy is specialized for buy and sell cases. So, once you decide whether you're buying or selling, you use one or the other and there are no more branches inside the class methods. It's essentially generating 2 code paths and you pick one of them with a single branch:

The problem here is that you're trying to alter the net request object instead of the uri object:

These are not indexes but rather keys generated by TextInputFormat, as explained here.

The class you supply for the input format should return key/value pairs of Text class. If you do not specify an input format class, the TextInputFormat is used as the default. Since the TextInputFormat returns keys of LongWritable class, which are actually not part of the input data, the keys will be discarded; only the values will be piped to the streaming mapper.

And since you do not have any mapper defined in your job, those key/value pairs are written straight out to the file system. So as the above excerpt hints, you need some sort of a mapper that would discard the keys. A quick-and-dirty is to use something already available to serve as a pass-through, like a shell cat command:

You can start by creating a dataframe with the lists of strings as rows and split each string by ~ using str.split. You can then slice the result selecting only the second term followed by another split, this time by *, setting expand=True:

I evaluated Boost Asio for use in high frequency trading a few years ago. To the best of my knowledge the basics are still the same today. Here are some reasons why I decided not to use it:

1. Asio relies on bind() style callbacks. There is some overhead here.
2. It is not obvious how to arrange certain low-level operations to occur at the right moment or in the right way.
3. There is rather a lot of complex code in an area which is important to optimize. It is harder to optimize complex, general code for specific use cases. Thinking that you will not need to look under the covers would be a mistake.
4. There is little to no need for portability in HFT applications. In particular, having "automatic" selection of a multiplexing mechanism is contrary to the mission, because each mechanism must be tested and optimized separately--this creates more work rather than reducing it.
5. If a third-party library is to be used, others such as libev, libevent, and libuv are more battle-hardened and avoid some of these downsides.

Related: C++ Socket Server - Unable to saturate CPU

This is the travis.yml I ended up with (working)

If string does not contain any ',' then string.split(',') will return a list with a single element, the entire string. In this case, string.split(',')[1] will obviously raiseIndexError.

li[0] == li[-1] in case li is a list with a single element.

The options -F -pgmF htfpp are switched on globally. This applies the HTF preprocessor to all the files of the test suite, including the autogenerated Paths_schemer.

The more scalable solution is to enable the preprocessor only on files that import Test.Framework, using the OPTIONS_GHC pragma in each one:

You need to use an or statement instead of an and statement. Time cannot be both "after" May 2016 and "before" May 2015. It has to be one or the other.