-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
airbyte/source-google-ads
connector's SPEC command does not succeed
#13580
Comments
airbyte/source-google-ads
connector's CHECK command does not succeedairbyte/source-google-ads
connector's SPEC command does not succeed
@evantahler are you running it against the
|
Weird! I just confirmed again and see the same error. Our Docker image SHAs match
I'll ask others to see if this is perhaps os-dependent. I'm on an M1 Mac... |
I can confirm, I am also getting the same error as @evantahler:
(also on an M1 Mac) |
And on an Ubuntu box, things work OK!
I guess the thing to do is bump the version and publish the connector again with both ARM and AMD builds. I'll do that via #13624 |
Oops! The image is already published multi-arch (thanks @pedroslopez) - https://hub.docker.com/r/airbyte/source-google-ads/tags However,
|
Interestingly enough, running the image for amd64 does work fine (airbyte/source-google-ads is published for multiple architectures):
So there seems to be something different between the builds |
Ok! #13624 builds and works on M1 now - thanks for the protobuf hint @davydov-d! |
it seems like pinning that package degraded performance..I'm now trying to figure out how big is the time gap. if it's not critical - I will increase the timeout |
@evantahler could you please try version 3.20.0 or 3.20.1? both were released after the google-ads 14.1.0 we use, and it seems they are quite compatible. upd: 3.20.0 works fine on both Mac M1 and Ubuntu, but conflicts with google-ads dependency. I'll try to bump google-ads to 15.1.1, that should do the trick |
Done! Validated both for Ubuntu and Mac M1 - works. @evantahler pls have a look at the PR, I will publish new version as soon as you approve it |
The text was updated successfully, but these errors were encountered: