-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
fix(bigquery/storage/managedwriter): fix double-close error, add tests #4502
fix(bigquery/storage/managedwriter): fix double-close error, add tests #4502
Conversation
Writing tests picked up the error, so hooray.
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.
Just a couple of small things
if err != nil { | ||
t.Errorf("couldn't get stream info: %v", err) | ||
} | ||
log.Printf("info id: %s type: %s", info.GetName(), info.GetType().String()) |
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.
If you want to log here I would recommend t.Log
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.
Sorry, this (and the other comment) was due to some debugging I was doing, which exposed the need to backend whitelist some functionality. Cleared it out.
Writing tests picked up the error, so hooray.
BufferedStream integration test exposed that while the API surface is in preview without special requirements, advanced features such as the FlushRows rpc used by BufferedStream does. This has been whitelisted for test projects, but we'll want to add this to doc.go when I start that PR.
Towards #4366