Using statically-sized buffers for dynamically-generated content is never the best solution, and we've run into a situation where we are consistently rubbing up against the initial 1024 character buffer size. Bumping it to 4096 for now seems to be sufficient, but a better solution would be to utilize a dynamically sized buffer, possibly via `std::string` so that memory management is handled implicitly.

There are some internals to the usage of the buffer that cause any change to it's size in `MsgPack.h` to result in a segfault. More research is needed to figure out where exactly the buffer gets used and whether its usage can be replaced by `mpack_writer_init_growable` for mostly-automatic memory management.