APITools | Test Repo for GitHub API Tools | REST library

After giving up on this I decided to reinstall one last time the whole google-cloud-sdk suite, but this time using the snap version. Installing it via snap solved the issue for me. I think this points to some issue with my environment that was bypassed thanks to the snap containerization.

So no clear answer here, but if anyone is experiencing the same problem giving a chance to snap may solve the issue as it did for me

schema isn't a valid keyword within a schema in OpenAPI 3.0.x

You probably want to use an allOf to say that your schema must a satisfy two (or more) subschemas:

I took your string with Chinese characters and was able to reproduce your error. I fixed it after updating to gsutil 4.62. Here's the merged PR and issue tracker as reference.

Update Cloud SDK by running:

I found the reason for the error and the solution to fix it if anyone is facing this issue.

Reason - The App engine Flexible Service Account was accidentally deleted from the google cloud project. As mentioned in this link - service-account

You have to put your security group in your VPC using VpcId property:

Yes, the pattern will work. In general it catches any failure that can be caught (sometimes things fail so badly that the processing stops entirely).

In your specific case, the stacktrace includes this region of BigQueryIO and you can see the failed rows output to the dead letter PCollection just below, here.

In order to further contribute to the community I am posting the answer based on my comment above.

Firstly, you should try to upgrade the packages using the command:

pip install --upgrade pandas-gbq 'google-cloud-bigquery[bqstorage,pandas]'

Then, instead of using the to_dataframe() method you can use the read_gbq(), which loads data from BigQuery using the environment's default project, as follows:

It is an opened investigation on this issue:

permission denied error when exporting asset to GCS or BigQuery

It seems that you have to impersonate the built-in service account service-xxxxxxxx@gcp-sa-cloudasset.iam.gserviceaccount.com and to add the Storage Admin role to it.

Also you will have to add the roles roles/bigquery.jobUser and roles/bigquery.dataEditor to the service account service-xxxxxxxx@gcp-sa-cloudasset.iam.gserviceaccount.com where xxxxxx is the project id.

To make it clearer, you should create a services folder for wrapping your API calls with the backend. since you are using Axios, create a new folder, and call it services. then create an HttpService.js as a reusable component of Axios for initializing the connection for future use.