| commit | 06cb606a14a5a9fbf61ddf0da051b8454bffdf99 | [log] [tgz] |
|---|---|---|
| author | Olav Loite <koloite@gmail.com> | Fri Oct 18 18:52:24 2019 +0200 |
| committer | Tyler Bui-Palsulich <tbp@google.com> | Tue Jan 07 02:45:32 2020 +0000 |
| tree | 386d895f3b45a958958795e1097d5abdfa70d87b | |
| parent | cd75e49f0f9fb158a34c98a4ba560053679d6201 [diff] |
spanner: Track stacktrace of sessionPool.take() Sessions are automatically checked out of the session pool by the client library when one is needed, and returned to the pool when the user closes the transaction and/or row iterator that was used. If the user however forgets to close the transaction or row iterator, the session will leak and the user will eventually get an error while trying to start a transaction. This error can occur in a completely unrelated part of the application than the part that causes the session leak, which makes these bugs very hard to debug and track down. This change allows the user to instruct the session pool to keep track of the stacktrace of each goroutine that checks out a session from the pool. The stacktraces of all checked out sessions + the time the session was taken from the pool is then included in the error that is returned when the session pool has been exhausted and no more sessions can be returned. This option can be used to track down the part(s) of the application that is causing a session leak. This feature is disabled by default, and must be enabled specifically by a user to have any effect. Updates #1616. Change-Id: I2ba84b65f391a99d0bed364d2a8e94f7467e3704 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/47150 Reviewed-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Cody Oss <codyoss@google.com> Reviewed-by: Tyler Bui-Palsulich <tbp@google.com>
Go packages for Google Cloud Platform services.
import "cloud.google.com/go"
To install the packages on your system, do not clone the repo. Instead:
Change to your project directory:
cd /my/cloud/project
Get the package you want to use. Some products have their own module, so it's best to go get the package(s) you want to use:
$ go get cloud.google.com/go/firestore # Replace with the package you want to use.
NOTE: Some of these packages are under development, and may occasionally make backwards-incompatible changes.
NOTE: Github repo is a mirror of https://code.googlesource.com/gocloud.
Alpha status: the API is still being actively developed. As a result, it might change in backward-incompatible ways and is not recommended for production use.
Beta status: the API is largely complete, but still has outstanding features and bugs to be addressed. There may be minor backwards-incompatible changes where necessary.
Stable status: the API is mature and ready for production use. We will continue addressing bugs and feature requests.
Documentation and examples are available at godoc.org/cloud.google.com/go
We support the two most recent major versions of Go. If Google App Engine uses an older version, we support that as well.
By default, each API will use Google Application Default Credentials for authorization credentials used in calling the API endpoints. This will allow your application to run in many environments without requiring explicit configuration.
client, err := storage.NewClient(ctx)
To authorize using a JSON key file, pass option.WithCredentialsFile to the NewClient function of the desired package. For example:
client, err := storage.NewClient(ctx, option.WithCredentialsFile("path/to/keyfile.json"))
You can exert more control over authorization by using the golang.org/x/oauth2 package to create an oauth2.TokenSource. Then pass option.WithTokenSource to the NewClient function: snip:# (auth-ts)
tokenSource := ...
client, err := storage.NewClient(ctx, option.WithTokenSource(tokenSource))
Contributions are welcome. Please, see the CONTRIBUTING document for details. We‘re using Gerrit for our code reviews. Please don’t open pull requests against this repo, new pull requests will be automatically closed.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. See Contributor Code of Conduct for more information.