Peter von der Ahé

I think this should be fixed when we fix #206.

The C++ client (fletch) tells the persistent process the absolute path to the fletch program. This path will change if you move the SDK. So I think I can fix...

I don't think this is relevant for fixit. This issue doesn't impact our users as we only support a reduced set of features in incremental "production" mode.

See my comment in https://github.com/dart-lang/fletch/issues/172#issuecomment-145214186. I guess I forgot to remove shutdown. However, it is actually a bug if shutdown doesn't work as this is an indication that the process...

I have a couple of concerns about adding a build bot step: 1. It makes the build bot more complicated, and testing modifications to the buildbot is complicated (not something...

The `fletch` binary looks for an environment variable named `FLETCH_SOCKET_FILE`.

@ricowind I don't understand why this relates to taskkill.

I think the what should happen is the following: ``` console $ fletch/out/DebugX64/fletch attach tcp_socket pi2:47704 $ fletch/out/DebugX64/fletch attach tcp_socket pi2:47704 Already connected to Fletch VM on pi2:47704; Try running...

I like `detach`.

As @lukechurch points out, as long as disconnecting from the Fletch VM isn't a reversible operation, we shouldn't call it `detach`. We should change `shutdown` to shutdown the current session...