Without this decoding, the stream of bytes returned from the marathon
describe call were being interpreted as a 'collection.Sequence' in the
subsequent 'emitter.publish()' call. This was causing the subesequnt
JSON encoding to blow up since it was interpeting it as the wrong type.