Raul Ronald Galea

@hcho3 Removing any of the 5 hyperparameters from the grid makes it work correctly. It is somehow these exact 5 that cause the issue.

I was following the setup presented on the criu C API [page](https://criu.org/C_API) under the **Preparation** section. Quoting relevant information: > Note that a CRIU service must be running at that...

I'm planning to dump child processes from within the same program. As far as I understand this requires the local RPC service (since criu cannot dump itself?), so I should...

I see, I'll just go with using the CRIU binary version as you recommend then. The `criu_check()` function still returns -52 though, even without setting the service. It does not...

> It would be great if we add this feature to the helm chart, but it won't be an easy task, because to implement it we will need to add...

I've had a look at how the helm chart is structured and my approach would be as follows: First, identify the minimum options that need to be configurable for the...

+1 would be a great feature to have. It's common to have specific workers (services) listening on specific task queues. Exposing the size of a given task queue would be...

+1 this would be a very relevant feature. Otherwise, navigating through potentially thousands of `running` workflows is not really feasible...

Just wanted to mention that I got the same error, but happened to me in a more convoluted way. The resource somehow initially became tainted, I couldn't untaint it after....

Update: I now know exactly how to reproduce my case. The Google CloudSQL [docs](https://cloud.google.com/sql/docs/mysql/iam-authentication#user_and_service_account_administration) say: "After you've added the IAM user to the database, you need to grant database privileges...