chore(spanner): fix some go vet issues#9758
chore(spanner): fix some go vet issues#9758gcf-merge-on-green[bot] merged 10 commits intogoogleapis:mainfrom
Conversation
These are not problems per se, however they end up as noise in `go vet` output.
…able structs While the copying in these locations doesn't change the result, the copies end up as noise in go vet output.
noahdietz
left a comment
There was a problem hiding this comment.
Approving again since this went a tad stale. Thanks for the tweaks @egonelbre
|
Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot. |
|
Looks like this failed: But, as far as I can tell this PR doesn't change anything about it. |
|
Running presubmits again, hopefully just a flake |
Looks like it cleared. I'll baby sit the PR to submission - I'm merging other stuff atm |
Failure on last run was a data race...we should probably look into that separately @rahul2393 @harshachinta |
|
@noahdietz I usually can reproduce similar issues with targeting specific tests and then running the tests multiple times... e.g. As far as I can tell from the trace -- it's happening because the clients are not waiting for every started goroutine to be finished. Nothing is waiting this goroutine to be finished: And it seems the tracing is using global vars, which then ends up causing data races. Without knowing the exact details, I would add a waitgroup / errgoup into sessionClient and when calling close it then must wait for all the started goroutines to be finished. |
|
@noahdietz I ended up creating #10095 -- I'm not yet sure whether it'll pass the test, but at least it should reduce the likelihood of a race. |
This fixes some trivial go vet issues. Each commit is dedicated to specific issue class (mostly).