Add 'runnable' to Isolate service response

Add 'runnable' to Isolate service response

BUG=
R=rmacnak@google.com

Review URL: https://codereview.chromium.org/1676233003 .

[Bill Hesse, 2016-02-09 10:11:49]

whesse@google.com changed reviewers:
+ johnmccutchan@google.com
- rmacnak@google.com

[Bill Hesse, 2016-02-09 10:11:49]

This change did not merge cleanly into stable, because the protocol minor
version had changed to 3.1 with other unrelated(?) changes.

This proposed merge creates a new version number 3.3 used only for this stable
version, that includes the protocol change in 3.2 but not that in 3.1.

Please verify that none of the other changes to the vm service need to be
merged, and that bumping the version number this way is how you want to solve
the problem.  I guess you would then bump bleeding-edge to 3.4 in the next
change to the protocol.

[Cutch, 2016-02-09 15:43:12]

On 2016/02/09 10:11:49, Bill Hesse wrote:
> This change did not merge cleanly into stable, because the protocol minor
> version had changed to 3.1 with other unrelated(?) changes.
> 
> This proposed merge creates a new version number 3.3 used only for this stable
> version, that includes the protocol change in 3.2 but not that in 3.1.
> 
> Please verify that none of the other changes to the vm service need to be
> merged, and that bumping the version number this way is how you want to solve
> the problem.  I guess you would then bump bleeding-edge to 3.4 in the next
> change to the protocol.

Hi Bill,

Thanks for doing this but we can't bump the protocol version like this CL does.
I will discuss with people here about whether or not we just want to leave 1.4.x
in it's current state or merge all the changes so that the service protocol is
up to date with respect to the bleeding_edge.

John