DM shows dirty data globally rather than on the branch

[eliasweingaertner]

Surfaced during Kubecon hackathon:

dm dot show shows dirty data globally and refulles to pull, even if the dirty data exists on a different branch rather than the active one.

This causes error messages like

dm pull dothub Pulling admin/moby_counter from dothub:elias/moby_counter Response '{"jsonrpc":"2.0","error":{"code":-32000,"message":"Aborting because there are 0.01 MiB of uncommitted changes on volume where data would be written. Use 'dm reset' to roll back.","data":null},"id":8674665223082153551} ' yields error Aborting because there are 0.01 MiB of uncommitted changes on volume where data would be written. Use 'dm reset' to roll back.

See also attached screenshot

[lukemarsden]

Plan to fix

• [ ] Address the underlying issue, possibly related to https://github.com/dotmesh-io/dotmesh/issues/90
• [ ] Move the display of dirty data in dm dot show to be per branch
• [ ] Check that it fixes the pulling issue described above