gax | Project for Shin'en GAX Sound Engine

Looks like they key itself might not be correctly visible to the pod. I would start by getting into the pod with kubectl exec --stdin --tty -- /bin/bash and ensuring that the /var/key.json (per your config) is accessible and has the correct credentials.

The following would be a good way to mount the secret:

This code should work to authenticate the firebase-admin package:

You have to run go mod tidy.

Tidy makes sure go.mod matches the source code in the module. [...] It also adds any missing entries to go.sum and removes any unnecessary ones.

The reason why this might happen on debug and not happen on compile/build — depending on what you actually did before entering in debug mode, — might be:

• this bug
• or that the dependency with the bad sum was used only in testing, and go build ignores files ending in _test.go

When compiling packages, build ignores files that end in '_test.go'.

I posted this answer to make a solution from the comment section more visible.

As it was suggested by @John Hanley and confirmed by @SmartCoder this issue was solved by adding to the Docker file lines below:

When you want Project Y (where your data fusion is in) to use resources from Project X (where the DLP is in) is to add the data fusion and compute engine service accounts of Project Y to Project X.

Notes:

• Data Fusion service account: service-xxxxxxx@gcp-sa-datafusion.iam.gserviceaccount.com
• Default compute engine service account: xxxxx-compute@developer.gserviceaccount.com

Project Y:

1. Go to IAM & Admin -> IAM
2. Click View by: "Members"
3. Tick checkbox "Include Google-provided role grants"
4. Look for service-(project number of Project Y)@gcp-sa-datafusion.iam.gserviceaccount.com and (project number of Project Y)-compute@developer.gserviceaccount.com
5. Add role "DLP Administrator" for service-(project number of Project Y)@gcp-sa-datafusion.iam.gserviceaccount.com

Project X:

1. Go to IAM & Admin -> IAM
2. Click Add
3. Under New Members, put service-(project number of Project Y)@gcp-sa-datafusion.iam.gserviceaccount.com
4. Grant role of "DLP Admininistrator"
5. Repeat step 2 to step 4 but this time put in (project number of Project Y)-compute@developer.gserviceaccount.com

Now that you are able to set the permissions, Go back to Project Y and update your Redact to point to Project X.

1. Go to Data Fusion -> Studio
2. Click Redact-> Properties
3. Put the template ID you created in Project X, in my sample it is "test_template"
4. Under Project ID, put the Project ID of Project X
5. Run your Data Fusion pipeline

you would want to first speak the 'step 1' then use thread.sleep(2000); then speak 'take a deep breath'

The error means that your Function Builder is missing the required parameters in order to create the function. If you try to create a function via Cloud Console, you're required to enter details such as function name, entrypoint, runtime, trigger type, and source code.

I've already reached out to the engineers and they are now informed with regards to the lack of details in the log output.

As a solution, here's a sample code that will create a Cloud Function running on Java 11. Of course you can always choose any type of runtime you want:

You can get the columnSpecId by calling ListColumnSpecs on the TableSpec: https://googleapis.dev/java/google-cloud-clients/latest/com/google/cloud/automl/v1beta1/AutoMlClient.html#listColumnSpecs-com.google.cloud.automl.v1beta1.ListColumnSpecsRequest-

Something like this:

We have discovered that the issue occurred because of we were using c# built-in ManualResetEvent from an async code. Seems like it caused some sort of a deadlock for the application threads.

Using SemaphoreSlim instead fixed the issue.