Willy Nojopranoto

It's unlikely we'll get that to work in google-cls-v2 for two reasons: 1) The Lifesciences API (google-cls-v2 provider) is going away in favor of the Batch API (google-batch) provider. 1)...

Hi @FreshAirTonight We released [v0.4.12](https://github.com/DataBiosphere/dsub/releases/tag/v0.4.12) yesterday which includes support to mount GCS buckets with the google-batch provider. When you get the chance, can you verify if it resolves your issues?

That's great, thanks @FreshAirTonight ! On your issues: 1) I've been trying to reproduce this one but haven't seen it so far. What I have been able to figure out...

> I realized that the issue was caused by another version of protobuf. I have purged that package and now the issue is gone. Thats great to hear! I'll close...

One last comment here for others who may have issues with google-batch and protobuf: I was able to reproduce an issue with protobuf 3.18.0. With 3.19.0, things seem to be...

Hi @hnawar : We just put out release [0.4.11](https://github.com/DataBiosphere/dsub/releases/tag/v0.4.11), which includes: - Extend batch support for network, subnetwork, private IP, accelerator, min cpu, min ram, boot disk, and machine type....

Hi @nick-youngblut ~~Thanks for reporting. There was an update in the Batch API that changed the way log files were written to disk. We're in the process of making the...

Thanks @nick-youngblut . I misunderstood the issue. The confusion comes from how the API pulls the docker image. From https://cloud.google.com/life-sciences/docs/reference/rest/v2beta/projects.locations.pipelines/run#Action in the `imageUri` section it mentions "Note that all images...

> Clarification question: Are jobs that are QUEUED due to resource quotas, but listed as RUNNING (i.e. Status: `VM starting (awaiting worker checkin)`) constrained by the same timeout restriction as...

By `Mount reference` I'm assuming they mean this object in the request: https://cloud.google.com/life-sciences/docs/reference/rest/v2beta/projects.locations.pipelines/run#mount . There is a read-only flag here. For persistent and existing disks, dsub always mounts this read-only...