-
Notifications
You must be signed in to change notification settings - Fork 555
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
Add autogenerated Bigtable library #1786
Conversation
- Remove a bad type check - Rename a conflicting class name
google-cloud-bigtable/.rubocop.yml
Outdated
Exclude: | ||
- "google-cloud-bigtable.gemspec" | ||
- "lib/google/bigtable/v2/**/*" | ||
- "lib/google/cloud/bigtable/v2/**/*" |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
google-cloud-bigtable/.rubocop.yml
Outdated
@@ -2,7 +2,9 @@ AllCops: | |||
Exclude: | |||
- "google-cloud-bigtable.gemspec" | |||
- "lib/google/bigtable/v2/**/*" |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
@blowmage @quartzmo The continued failure seems to be from the jsondoc task.
Any idea what this means? |
Never mind -- this appears to be from improper usage of the |
I'm not sure why the CI build is still failing (now in VideoIntelligence). The error message looks like the issue that was fixed in googleapis/gapic-generator#1643, which shouldn't happen in VideoIntelligence, unless the tests are being run in the same environment across gems. It's also unclear to me why this PR would trigger a failure if it was succeeding previously. |
From the failed build:
@geigerj Isn't this error a result of the class being defined twice with inheritance?
|
@quartzmo Right, several of the GAPICs define a class by this name in their unit tests, but does/should the test care if they're defined in different GAPICs? And I'm unsure why this failure didn't come up in the last successful build, which already contains two GAPICs with such unit tests ( |
Hooray, CI passes now! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Glad to see this green.
Note: This is not for release. Engineers from the BigTable team will be writing the manual layer for the client library on top of this GAPIC library. They would prefer to develop in master unless there's a reason to work in another branch.