Bryan Crampton

Not sure if you want this included in your project, but it was a feature I was looking for and I added it. I also renamed references to "like" to...

LocalJobProvider should return an accurate start-time

1

A job's `start-time` for the Google provider reflects "The time at which the job began to run" [docs](https://cloud.google.com/genomics/reference/rest/Shared.Types/OperationMetadata). This field is only populated once the vm has been created on...

Currently calling `dsub.run(...)` from python causes output of the following form in stdout: ``` Launched job-id: echo--bryancrampton--171108-161028-235004 To check the status, run: dstat --provider local --jobs 'echo--bryancrampton--171108-161028-235004' --status '*' To...

Currently the `StubJobProvider` stores operation statuses [as a tuple](https://github.com/googlegenomics/dsub/blob/57ba7da5b071444e2849abe95c0c5af99bf2f24e/dsub/providers/stub.py#L49) with the status string and date. This causes consumers of dstat to add provider-specific logic to parse out the status: ```...

I think it would be useful for python users building on top of dsub to have access to some sort of constant defining acceptable dsub statuses.

It would be nice for testing project which depend on dsub if the `StubJobProvider` supported `submit_job` and `delete_job` methods by modifying its underlying `_operations` array rather than requiring mocking those...

Currently we are hard coding the `FieldDataType` for `queryExtensions` in [UI code](https://github.com/DataBiosphere/job-manager/blob/master/ui/src/app/shared/common.ts#L31). Ideally this would be part of the `CapabilitiesResponse` to remove coupling of the UI and API.