-
Notifications
You must be signed in to change notification settings - Fork 381
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
Bump cloud.google.com/go/spanner from 1.42.0 to 1.45.1-0.20230421054906-c65254ce3c22 #2957
Bump cloud.google.com/go/spanner from 1.42.0 to 1.45.1-0.20230421054906-c65254ce3c22 #2957
Conversation
aab8bb8
to
dc71ff5
Compare
/gcbrun |
2 similar comments
/gcbrun |
/gcbrun |
We are hitting another obstacle. The error |
Thanks for looking into this @roger2hk. It looks like this is deep inside the internals of the spanner transaction. What I'm seeing is the transaction being released which marks it as closed. Within our code, the transaction has state What I haven't yet determined is whether this is a bug in the spanner library, or whether we've always been doing something wrong here and it's only coming to light now. (edit: what I should have added is that in the previous version of the spanner library the tx state was always |
https://github.com/google/trillian/blob/master/storage/cloudspanner/tree_storage.go#L108 Before (edit: git blame shows this bit of code is only 2 days old: googleapis/google-cloud-go#7712) |
Out of curiosity I synced to the commit before that PR. At that version, the tests timeout due to the deadlock that the PR fixes. It looks like there are a lot of big breaking changes going into this library at the current time. We need to step back and determine whether we get actively involved in this, or whether we stay with the current working version of this library, let the dust settle from these changes, and then hope that things are working again. |
Thanks @rahul2393 for looking into this. |
Bumps [cloud.google.com/go/spanner](https://github.com/googleapis/google-cloud-go) from 1.42.0 to 1.45.0. - [Release notes](https://github.com/googleapis/google-cloud-go/releases) - [Changelog](https://github.com/googleapis/google-cloud-go/blob/main/CHANGES.md) - [Commits](googleapis/google-cloud-go@spanner/v1.42.0...spanner/v1.45.0) --- updated-dependencies: - dependency-name: cloud.google.com/go/spanner dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
63a6ade
to
3f56694
Compare
/gcbrun |
Issue fixed in googleapis/google-cloud-go#7809 but 1.45.1 is not yet released (googleapis/google-cloud-go#7767). @mhutchinson Please review to see if it's good to go. |
v1.45.1 was just released by @Rahul2923. I will let Dependabot handle the remaining upgrade. |
Bumps cloud.google.com/go/spanner from 1.42.0 to 1.45.0.
Release notes
Sourced from cloud.google.com/go/spanner's releases.
Commits
c43900b
chore(main): release spanner 1.45.0 (#7462)688d4ab
fix: deadlock with inline begin transaction when first statement response is ...7afc98a
chore(internal/postprocessor): add MoveSnippets to main.go (#7523)a6c6701
refactor(bigquery): amend name for MaxTimeTravel on datasets (#7707)22a666c
feat(bigquery): expose dataset MaxTimeTravelHours (#7706)3b8bfb4
feat(bigquery/storage/managedwriter): expose connection multiplexing as exper...e660af8
chore: cleanup gapicgen a bit (#7703)4fedc34
chore(storage): handle object metadata (grpc) (#7688)2a5c165
chore: onboard compute to owlbot (#7705)7a9e211
feat(bigquery): Add Iceberg as DataFormat option. (#7155)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)