-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: grpc/grpc-java
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.45.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: grpc/grpc-java
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.45.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 41 files changed
- 4 contributors
Commits on Mar 8, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 62073d9 - Browse repository at this point
Copy the full SHA 62073d9View commit details -
xds: Don't end status with '.' in XdsNameResolver (#8958) (#8965)
2a45524 introduced '.' to the end of some status descriptions. We typically don't end status descriptiosn in periods, but that's minor. In this case though if the causal status ends in period then the new status will end in two periods, which could easily be confusing to users. Co-authored-by: Eric Anderson <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 6844f06 - Browse repository at this point
Copy the full SHA 6844f06View commit details
Commits on Mar 22, 2022
-
rls: fix wrong grpcKeybuilder field name (#8999)
The `grpcKeybuilders` [field](https://github.com/grpc/grpc-proto/blob/9fb243ce29b2e2576d3ef4fa2bd00ecba36aee31/grpc/lookup/v1/rls_config.proto#L176) should not be `grpcKeyBuilders` in json format. The mistake in Java was introduced since the [beginning](0fd4975#diff-585b634c79155b4ac9417f7805e1b9d5f6d5c11a940c88e27fdf53c209e619cfR104).
Configuration menu - View commit details
-
Copy full SHA for 97e215a - Browse repository at this point
Copy the full SHA 97e215aView commit details -
rls: remove wrong empty address checke for child lb (#9005)
We shouldn't require addresses to be non-empty for the child lb of rls_lb. That might be a right requirement when the child lb is grpclb, but in our new usecase, the child lb will be cds lb and will only work if empty address is allowed. Fixing b/223866089#comment24
Configuration menu - View commit details
-
Copy full SHA for 1234fd3 - Browse repository at this point
Copy the full SHA 1234fd3View commit details
Commits on Mar 23, 2022
-
netty: Support pseudo headers in all GrpcHttp2RequestHeaders methods
The previous code assumed that only gRPC would be using these methods. But twice now Netty has made a change (generally relating to security) that used a method for pseudo headers that previously wasn't supported. Let's stop the whack-a-mole and just implement them all. This restores compatibility with Netty 4.1.75.Final. Fixes #8981
Configuration menu - View commit details
-
Copy full SHA for 8bc9b3b - Browse repository at this point
Copy the full SHA 8bc9b3bView commit details
Commits on Mar 24, 2022
-
Configuration menu - View commit details
-
Copy full SHA for a8d887f - Browse repository at this point
Copy the full SHA a8d887fView commit details
Commits on Mar 29, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 81813c4 - Browse repository at this point
Copy the full SHA 81813c4View commit details -
Configuration menu - View commit details
-
Copy full SHA for ff750a5 - Browse repository at this point
Copy the full SHA ff750a5View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.45.0...v1.45.1