Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error while executing onJobBucketChange.functions #33

Open
dollyagarwal opened this issue Jan 9, 2020 · 8 comments
Open

Error while executing onJobBucketChange.functions #33

dollyagarwal opened this issue Jan 9, 2020 · 8 comments

Comments

@dollyagarwal
Copy link

Voice-builder has been deployed to the GCP project and a job is created from the dashboard. But the status of the job stays at Exporting Resources. Upon checking the logs, I saw that there was an error while executing the onJobBucketChange funciton. PFB the screenshot:

image

Moreover, on further debugging, I found that pipelineInfo.json is not created for the job. The files in the job bucket are as shown in the screenshot below:

image

I am not sure, what is going wrong? I appreciate any help provided.

@pasindud
Copy link
Contributor

pasindud commented Jan 19, 2020

Hi
can you add a console.log(object) to https://github.com/google/voice-builder/blob/master/cloud_functions/functions/index.js#L35

then re-ran the voice building, and check the logs again.

@dollyagarwal
Copy link
Author

Hi, Thanks for your response. I added the console.log(object), here's the log:

image

@pasindud
Copy link
Contributor

pasindud commented Jan 20, 2020

After the change did you run voice building again ?

@dollyagarwal
Copy link
Author

Yes I did. I think the undefined displayed in the log is the object.

@pasindud
Copy link
Contributor

In which case instead of logging object can you do console.log(event)

@dollyagarwal
Copy link
Author

Here's the screenshot of the log:

screenshot

@thejaigoyal
Copy link

thejaigoyal commented May 12, 2020

Hey @dollyagarwal did you get the solution for this, I'm stuck on the same issue

@crazzywizard
Copy link

Hey @dollyagarwal I changed event.data in line 34 of index.js to just event and was able to resolve these errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants