Skip to content
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 google.golang.org/grpc from 1.29.1 to 1.30.0 in /instrumentation/labstack/echo #100

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 24, 2020

Bumps google.golang.org/grpc from 1.29.1 to 1.30.0.

Release notes

Sourced from google.golang.org/grpc's releases.

Release 1.30.0

API Changes

  • This release adds an xDS URI scheme called xds. This is the stable version of the scheme xds-experimental that was introduced in v1.28.0. xds-experimental scheme will be removed in subsequent releases so you must switch to xds scheme instead. xds scheme is a client side implementation of xDSv2 APIs. This allows a gRPC client written in Go to receive configuration from an xDSv2 API compatible server and use that configuration to load balance RPCs. In this release, only the virtual host matching, default path (“” or “/”) matching and cluster route action are supported. The features supported in a given release are documented here.
  • balancer: move Balancer and Picker to V2; delete legacy API (#3431)

Behavior Changes

  • grpclb, dns: pass balancer addresses via resolver.State (#3614)

New Features

  • balancer: support hierarchical paths in addresses (#3494)
  • client: option to surface connection errors to callers (#3430)
  • credentials: pass address attributes from balancer to creds handshaker. (#3548)
  • credentials: local creds implementation (#3517)
  • advancedtls: add fine-grained verification levels in XXXOptions (#3454)
  • xds: handle weighted cluster as route action (#3613)
  • xds: add weighted_target balancer (#3541)

Performance Improvements

  • transport: move append of header and data down to http2 write loop to save garbage (#3568)
  • server.go: use worker goroutines for fewer stack allocations (#3204)

Bug Fixes

  • stream: fix calloption.After() race in finish (#3672)
  • retry: prevent per-RPC creds error from being transparently retried (#3677, #3691)
  • cache: callback without cache's mutex (#3603)
  • client: properly check GRPC_GO_IGNORE_TXT_ERRORS environment variable (#3532)
  • balancergroup: fix connectivity state (#3585)
  • xds: use google default creds (#3673)
  • xds: accept either "" or "/" as the prefix for the default route (#3535)
  • xds: reject RDS response containing match with case-sensitive false (#3592)

Documentation

  • examples: add go.mod to make examples a separate module (#3546)
  • doc: update README for supported Go versions and travis for tests (#3516)
Commits
  • 1f47ba4 Change version to 1.30.0 (#3679)
  • ca0f900 retry: re-enable retrying on non-IO transport errors (#3691) (#3695)
  • b6d6ede xds: use google default creds (#3673)
  • eb11ffd retry: prevent per-RPC creds error from being transparently retried (#3677)
  • 9aa97f9 stream: fix calloption.After() race in finish (#3672)
  • d5bc6ec xds: Add cmpopts.EquateEmpty option in tests. (#3671)
  • 479df5e advancedtls: check error before deferring close (#3659)
  • ad51f57 protoc-gen-go-grpc: add requirement of embedding UnimplementedServer in servi...
  • 42eed59 xds: handle errors in xds_client (#3658)
  • cb7f5de xds: handle errors in xds resolver (#3651)
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.29.1 to 1.30.0.
- [Release notes](https://github.com/grpc/grpc-go/releases)
- [Commits](grpc/grpc-go@v1.29.1...v1.30.0)

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jun 24, 2020
@MrAlias MrAlias merged commit d8b0c8e into master Jun 24, 2020
@dependabot dependabot bot deleted the dependabot/go_modules/instrumentation/labstack/echo/google.golang.org/grpc-1.30.0 branch June 24, 2020 20:36
plantfansam referenced this pull request in plantfansam/opentelemetry-go-contrib Mar 18, 2022
This is to shrink the PR #100.

The only place where the registry.Variable type was used was metrics,
so just inline that type into its only user. The use of the
registry.Variable type in core.Key was limited to the Name field.

The stats package also used the registry.Variable type, but seems that
also only the Name field was used and the package is going to be
dropped anyway.
plantfansam referenced this pull request in plantfansam/opentelemetry-go-contrib Mar 18, 2022
* Drop dead event type

* Replace EventType from reader with one from exporter

* Do not concat the strings for string buffer

* Fill scope ID in events

That required renaming a variable, because it had the same name as the
type we wanted to assert later.

* Do not fail quietly when span context is busted
plantfansam referenced this pull request in plantfansam/opentelemetry-go-contrib Mar 18, 2022
* initial metrics work

* rename cumulative to counter

* rename bidirectional to nonmonotonic

* rename unidirectional to monotonic

* rename nonnegative to signed

this changes the default semantics a bit - before the change measure
could record negative values by default, now it can't.

The specification draft currently specifies both NonNegative and
Signed, but I think it's a mistake.

* rename instrument to descriptor

* license

* rework measurement values

* make measurement value a tagged union

* simplify to one kind of metrics

* add observers

* change some interfaces to match the spec

* keep integral measurement separate from floating ones

* remove duplicated measurement type

* add checking for options

* reorder some fields and functions

* rename a function

to avoid confusion between the Handle type and the Measure type

* drop disabled field from descriptor

* add back typed API for metrics

* make metric options type safe

* merge alternatives into a single bool

* make value kind name less stuttery

* fix observation callback prototype

* drop context parameter from NewHandle

* drop useless parameter names

* make descriptor an opaque struct

* use a store helper

* handle comment fixes

* reword Alternate comment

* drop the "any value" metrics

* make measurement value simpler

* document value stuff

* add tests for values

* docs

* do not panic if there is no span ID in the event
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants