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

chore(deps) bump grpcurl from 1.8.2 to 1.8.5 #7959

Merged
merged 1 commit into from
Oct 13, 2021
Merged

Conversation

bungle
Copy link
Member

@bungle bungle commented Oct 13, 2021

Summary

This is the first release that includes binaries for linux/s390x.
This is also the first release that includes Docker images for arm
platforms (we hope to add Docker images for s390x in the future).

Changes

Command-line tool
  • Some bugs have been addressed in the library used to parse proto
    source files. Previously grpcurl would accept proto source files
    that could not actually be compiled with protoc. The converse could
    also happen: grpcurl could reject some proto source files that could
    successfully be compiled with protoc. More details can be found in
    the release notes for the changes to the protoparse library,
    versions v1.10.0 and v1.10.1).
  • Some error conditions could cause grpcurl to "panic", where the tool
    aborts with a stack dump. These could be induced by providing proto
    source files with certain unusually high unicode code points (which
    would not actually be valid protobuf source). It could also be induced
    by unlucky timing of connectivity failure to RPC server when making
    a client-streaming or bidi-streaming RPC.
  • Adds support for specifying an environment variable SSLKEYLOGFILE,
    which indicates a file name. When set and using TLS for a connection,
    grpcurl will log the TLS key used, so that an external tool such as
    Wireshark can use the key to decrypt and inspect network packets.
Go package "github.com/fullstorydev/grpcurl"
  • Goroutines calling grpcurl.InvokeRPC could panic when calling client-
    streaming and bidi-streaming methods, if the stream could not be created
    (such as a connectivity issue). This panic has been fixed and an error
    will be returned instead.

### Summary

This is the first release that includes binaries for linux/s390x.
This is also the first release that includes Docker images for arm
platforms (we hope to add Docker images for s390x in the future).

#### Changes

##### Command-line tool

- Some bugs have been addressed in the library used to parse proto
  source files. Previously grpcurl would accept proto source files
  that could not actually be compiled with protoc. The converse could
  also happen: grpcurl could reject some proto source files that could
  successfully be compiled with protoc. More details can be found in
  the release notes for the changes to the protoparse library,
  versions v1.10.0 and v1.10.1).
- Some error conditions could cause grpcurl to "panic", where the tool
  aborts with a stack dump. These could be induced by providing proto
  source files with certain unusually high unicode code points (which
  would not actually be valid protobuf source). It could also be induced
  by unlucky timing of connectivity failure to RPC server when making
  a client-streaming or bidi-streaming RPC.
- Adds support for specifying an environment variable SSLKEYLOGFILE,
  which indicates a file name. When set and using TLS for a connection,
  grpcurl will log the TLS key used, so that an external tool such as
  Wireshark can use the key to decrypt and inspect network packets.

##### Go package "github.com/fullstorydev/grpcurl"

- Goroutines calling grpcurl.InvokeRPC could panic when calling client-
  streaming and bidi-streaming methods, if the stream could not be created
  (such as a connectivity issue). This panic has been fixed and an error
  will be returned instead.
@gszr gszr merged commit 853582c into master Oct 13, 2021
@gszr gszr deleted the chore/grpcurl-1.8.5 branch October 13, 2021 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants