Skip to content

Conversation

@philipsdoctor
Copy link

Fixes #5705 Allows objects copied with the storage mock to then be read.

@philipsdoctor philipsdoctor requested a review from a team as a code owner July 9, 2019 01:42
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

}

@Test
public void testCopyCanBeRead() {
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test reproduces the issue and fails without my fix. An object created by copy cannot be read without raising a NPE. This issue is fixed by this PR.

@philipsdoctor
Copy link
Author

philipsdoctor commented Jul 9, 2019

Hi,
When I check the google CLA site, I see that I am properly signed up through my organization, and that the email matches by github email and my git config email. I'm not sure why this check is failing, if you have any ideas, I'm happy to fix them.

@raphaelhamonnais
Copy link

Thx @philipsdoctor for proposing this change. I definitely support it.

@sduskis sduskis added the cla: yes This human has signed the Contributor License Agreement. label Jul 9, 2019
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@sduskis sduskis added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 9, 2019
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 9, 2019
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Jul 9, 2019
@chingor13 chingor13 added the api: storage Issues related to the Cloud Storage API. label Jul 9, 2019
@chingor13
Copy link
Contributor

I'm not sure what's up with the googlebot as the commit history looks correct.

@chingor13 chingor13 added cla: yes This human has signed the Contributor License Agreement. kokoro:force-run Add this label to force Kokoro to re-run the tests. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Jul 9, 2019
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 9, 2019
@philipsdoctor
Copy link
Author

philipsdoctor commented Jul 9, 2019

Looking into these test failures, apologies, I'll get it fixed up.

@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@chingor13 chingor13 added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 10, 2019
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 10, 2019
@philipsdoctor
Copy link
Author

@chingor13

  1. I removed the test in error, re-adding it, that was my mistake
  2. this speech-it error is a little vague, I'm not clear why this was non-mergeable?
[07:44:22][ERROR] Cannot check out non-mergeable pull request as if merged.
Please attach a kokoro:force-run label to re-run the Kokoro build when this happens on subsequent commits.

@codecov
Copy link

codecov bot commented Jul 10, 2019

Codecov Report

Merging #5707 into master will increase coverage by 0.48%.
The diff coverage is 85.71%.

Impacted file tree graph

@@             Coverage Diff              @@
##             master    #5707      +/-   ##
============================================
+ Coverage     46.72%    47.2%   +0.48%     
- Complexity    24647    25189     +542     
============================================
  Files          2351     2389      +38     
  Lines        256149   260580    +4431     
  Branches      29327    29527     +200     
============================================
+ Hits         119688   123018    +3330     
- Misses       127539   128587    +1048     
- Partials       8922     8975      +53
Impacted Files Coverage Δ Complexity Δ
...ud/storage/contrib/nio/testing/FakeStorageRpc.java 60.94% <85.71%> (-3.65%) 44 <0> (+2)
.../main/java/com/google/cloud/bigquery/BigQuery.java 73.3% <0%> (-5.14%) 0% <0%> (ø)
...n/java/com/google/cloud/bigquery/BigQueryImpl.java 78.36% <0%> (-1.64%) 93% <0%> (+36%)
...d/storage/contrib/nio/CloudStorageReadChannel.java 79.76% <0%> (-1.2%) 18% <0%> (-1%)
...e/cloud/bigquery/testing/RemoteBigQueryHelper.java 61.53% <0%> (-0.97%) 8% <0%> (+2%)
.../com/google/cloud/pubsub/v1/MessageDispatcher.java 85.12% <0%> (-0.74%) 23% <0%> (ø)
.../google/cloud/bigquery/spi/v2/HttpBigQueryRpc.java 5.84% <0%> (-0.26%) 3% <0%> (+1%)
...bigtable/admin/v2/BigtableInstanceAdminClient.java 98.9% <0%> (-0.23%) 69% <0%> (+25%)
...gle/cloud/bigtable/data/v2/BigtableDataClient.java 89.47% <0%> (-0.11%) 64% <0%> (+32%)
... and 48 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4bba989...b0aa248. Read the comment docs.

@chingor13 chingor13 added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 10, 2019
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 10, 2019
@JesseLovelace JesseLovelace added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 15, 2019
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 15, 2019
@JesseLovelace JesseLovelace merged commit d284774 into googleapis:master Jul 15, 2019
@JesseLovelace JesseLovelace mentioned this pull request Jul 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: storage Issues related to the Cloud Storage API. cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FakeStorageRpc generation support for copy fails on read

7 participants