fix: init dubbogo/grpc

Author: LaurenceLiZhixin

.github/workflows/testing.yml

@@ -101,9 +101,9 @@ jobs:
         if: contains(matrix.type, 'tests')
         run: |
           go version
-          go test ${{ matrix.testflags }} -cpu 1,4 -timeout 7m google.golang.org/grpc/...
-          cd ${GITHUB_WORKSPACE}/security/advancedtls && go test ${{ matrix.testflags }} -timeout 2m google.golang.org/grpc/security/advancedtls/...
-          cd ${GITHUB_WORKSPACE}/security/authorization && go test ${{ matrix.testflags }} -timeout 2m google.golang.org/grpc/security/authorization/...
+          go test ${{ matrix.testflags }} -cpu 1,4 -timeout 7m github.com/dubbogo/grpc-go/...
+          cd ${GITHUB_WORKSPACE}/security/advancedtls && go test ${{ matrix.testflags }} -timeout 2m github.com/dubbogo/grpc-go/security/advancedtls/...
+          cd ${GITHUB_WORKSPACE}/security/authorization && go test ${{ matrix.testflags }} -timeout 2m github.com/dubbogo/grpc-go/security/authorization/...
 
 
       # Non-core gRPC tests (examples, interop, etc)

.idea/.gitignore

@@ -22,7 +22,7 @@ How to get your contributions merged smoothly and quickly.
 
 - The grpc package should only depend on standard Go packages and a small number
   of exceptions. If your contribution introduces new dependencies which are NOT
-  in the [list](https://godoc.org/google.golang.org/grpc?imports), you need a
+  in the [list](https://godoc.org/github.com/dubbogo/grpc-go?imports), you need a
   discussion with gRPC-Go authors and consultants.
 
 - For speculative changes, consider opening an issue and discussing it first. If

.idea/grpc-go.iml

@@ -11,7 +11,7 @@ compression turned on, invoking `benchmain` in the following way may closely
 simulate your application:
 
 ```bash
-$ go run google.golang.org/grpc/benchmark/benchmain/main.go \
+$ go run github.com/dubbogo/grpc-go/benchmark/benchmain/main.go \
     -workloads=streaming \
   	-reqSizeBytes=1024 \
   	-respSizeBytes=1024 \
@@ -43,7 +43,7 @@ of payload sizes (first two columns) and the weight associated with that range
 Assume that `benchmain` is invoked like so:
 
 ```bash
-$ go run google.golang.org/grpc/benchmark/benchmain/main.go \
+$ go run github.com/dubbogo/grpc-go/benchmark/benchmain/main.go \
     -workloads=unary \
   	-reqPayloadCurveFiles=/path/to/csv \
   	-respPayloadCurveFiles=/path/to/csv
@@ -59,16 +59,16 @@ execute the benchmark with each combination independently. That is, the
 following command will execute four benchmarks:
 
 ```bash
-$ go run google.golang.org/grpc/benchmark/benchmain/main.go \
+$ go run github.com/dubbogo/grpc-go/benchmark/benchmain/main.go \
     -workloads=unary \
   	-reqPayloadCurveFiles=/path/to/csv1,/path/to/csv2 \
   	-respPayloadCurveFiles=/path/to/csv3,/path/to/csv4
 ```
 
-You may also combine `PayloadCurveFiles` with `SizeBytes` options. For example:
+You may also Combine `PayloadCurveFiles` with `SizeBytes` options. For example:
 
 ```
-$ go run google.golang.org/grpc/benchmark/benchmain/main.go \
+$ go run github.com/dubbogo/grpc-go/benchmark/benchmain/main.go \
     -workloads=unary \
   	-reqPayloadCurveFiles=/path/to/csv \
   	-respSizeBytes=1

.idea/modules.xml

@@ -2,16 +2,16 @@
 
 The preferred method for configuring message compression on both clients and
 servers is to use
-[`encoding.RegisterCompressor`](https://godoc.org/google.golang.org/grpc/encoding#RegisterCompressor)
+[`encoding.RegisterCompressor`](https://godoc.org/github.com/dubbogo/grpc-go/encoding#RegisterCompressor)
 to register an implementation of a compression algorithm.  See
 `grpc/encoding/gzip/gzip.go` for an example of how to implement one.
 
 Once a compressor has been registered on the client-side, RPCs may be sent using
 it via the
-[`UseCompressor`](https://godoc.org/google.golang.org/grpc#UseCompressor)
+[`UseCompressor`](https://godoc.org/github.com/dubbogo/grpc-go#UseCompressor)
 `CallOption`.  Remember that `CallOption`s may be turned into defaults for all
 calls from a `ClientConn` by using the
-[`WithDefaultCallOptions`](https://godoc.org/google.golang.org/grpc#WithDefaultCallOptions)
+[`WithDefaultCallOptions`](https://godoc.org/github.com/dubbogo/grpc-go#WithDefaultCallOptions)
 `DialOption`.  If `UseCompressor` is used and the corresponding compressor has
 not been installed, an `Internal` error will be returned to the application
 before the RPC is sent.

.idea/vcs.xml

@@ -32,8 +32,8 @@ in the route guide example [here][route-guide-stream].  Similar to clients,
 multiple services can be registered to the same server.
 
 [helloworld]: https://github.com/grpc/grpc-go/blob/master/examples/helloworld/greeter_client/main.go#L43
-[client-conn]: https://godoc.org/google.golang.org/grpc#ClientConn
-[stream]: https://godoc.org/google.golang.org/grpc#Stream
+[client-conn]: https://godoc.org/github.com/dubbogo/grpc-go#ClientConn
+[stream]: https://godoc.org/github.com/dubbogo/grpc-go#Stream
 [say-hello]: https://github.com/grpc/grpc-go/blob/master/examples/helloworld/greeter_server/main.go#L41
 [route-guide-stream]: https://github.com/grpc/grpc-go/blob/master/examples/route_guide/server/server.go#L126
 [multiplex-example]: https://github.com/grpc/grpc-go/tree/master/examples/features/multiplex

CONTRIBUTING.md

@@ -19,7 +19,7 @@ that registers itself, and is imported anonymously.  For example:
 ```go
 package proto
 
-import "google.golang.org/grpc/encoding"
+import "github.com/dubbogo/grpc-go/encoding"
 
 func init() {
 	encoding.RegisterCodec(protoCodec{})
@@ -29,7 +29,7 @@ func init() {
 ```
 
 For an example, gRPC's implementation of the `proto` codec can be found in
-[`encoding/proto`](https://godoc.org/google.golang.org/grpc/encoding/proto).
+[`encoding/proto`](https://godoc.org/github.com/dubbogo/grpc-go/encoding/proto).
 
 ### Using a `Codec`
 
@@ -95,7 +95,7 @@ function that registers itself, and is imported anonymously.  For example:
 ```go
 package gzip
 
-import "google.golang.org/grpc/encoding"
+import "github.com/dubbogo/grpc-go/encoding"
 
 func init() {
 	encoding.RegisterCompressor(compressor{})
@@ -105,7 +105,7 @@ func init() {
 ```
 
 An implementation of a `gzip` compressor can be found in
-[`encoding/gzip`](https://godoc.org/google.golang.org/grpc/encoding/gzip).
+[`encoding/gzip`](https://godoc.org/github.com/dubbogo/grpc-go/encoding/gzip).
 
 ### Using a `Compressor`
 
@@ -115,7 +115,7 @@ By default, gRPC does not register or use any compressors.  To use a
 ```go
 package myclient
 
-import _ "google.golang.org/grpc/encoding/gzip"
+import _ "github.com/dubbogo/grpc-go/encoding/gzip"
 ```
 
 `Compressor`s, by definition, must be symmetric, so the same desired

Documentation/benchmark.md

@@ -29,33 +29,33 @@ For an example of how to configure client and server to use OAuth2 tokens, see
 ## Validating a token on the server
 
 Clients may use
-[metadata.MD](https://godoc.org/google.golang.org/grpc/metadata#MD)
+[metadata.MD](https://godoc.org/github.com/dubbogo/grpc-go/metadata#MD)
 to store tokens and other authentication-related data. To gain access to the
 `metadata.MD` object, a server may use
-[metadata.FromIncomingContext](https://godoc.org/google.golang.org/grpc/metadata#FromIncomingContext).
+[metadata.FromIncomingContext](https://godoc.org/github.com/dubbogo/grpc-go/metadata#FromIncomingContext).
 With a reference to `metadata.MD` on the server, one needs to simply lookup the
 `authorization` key. Note, all keys stored within `metadata.MD` are normalized
-to lowercase. See [here](https://godoc.org/google.golang.org/grpc/metadata#New).
+to lowercase. See [here](https://godoc.org/github.com/dubbogo/grpc-go/metadata#New).
 
 It is possible to configure token validation for all RPCs using an interceptor.
 A server may configure either a
-[grpc.UnaryInterceptor](https://godoc.org/google.golang.org/grpc#UnaryInterceptor)
+[grpc.UnaryInterceptor](https://godoc.org/github.com/dubbogo/grpc-go#UnaryInterceptor)
 or a
-[grpc.StreamInterceptor](https://godoc.org/google.golang.org/grpc#StreamInterceptor).
+[grpc.StreamInterceptor](https://godoc.org/github.com/dubbogo/grpc-go#StreamInterceptor).
 
 ## Adding a token to all outgoing client RPCs
 
 To send an OAuth2 token with each RPC, a client may configure the
 `grpc.DialOption`
-[grpc.WithPerRPCCredentials](https://godoc.org/google.golang.org/grpc#WithPerRPCCredentials).
+[grpc.WithPerRPCCredentials](https://godoc.org/github.com/dubbogo/grpc-go#WithPerRPCCredentials).
 Alternatively, a client may also use the `grpc.CallOption`
-[grpc.PerRPCCredentials](https://godoc.org/google.golang.org/grpc#PerRPCCredentials)
+[grpc.PerRPCCredentials](https://godoc.org/github.com/dubbogo/grpc-go#PerRPCCredentials)
 on each invocation of an RPC.
 
 To create a `credentials.PerRPCCredentials`, use
-[oauth.NewOauthAccess](https://godoc.org/google.golang.org/grpc/credentials/oauth#NewOauthAccess).
+[oauth.NewOauthAccess](https://godoc.org/github.com/dubbogo/grpc-go/credentials/oauth#NewOauthAccess).
 Note, the OAuth2 implementation of `grpc.PerRPCCredentials` requires a client to use
-[grpc.WithTransportCredentials](https://godoc.org/google.golang.org/grpc#WithTransportCredentials)
+[grpc.WithTransportCredentials](https://godoc.org/github.com/dubbogo/grpc-go#WithTransportCredentials)
 to prevent any insecure transmission of tokens.
 
 # Authenticating with Google

Documentation/compression.md

@@ -16,7 +16,7 @@ And concept of [metadata](https://grpc.io/docs/guides/concepts.html#metadata).
 
 ## Constructing metadata
 
-A metadata can be created using package [metadata](https://godoc.org/google.golang.org/grpc/metadata).
+A metadata can be created using package [metadata](https://godoc.org/github.com/dubbogo/grpc-go/metadata).
 The type MD is actually a map from string to a list of strings:
 
 ```go
@@ -127,7 +127,7 @@ Metadata that a client can receive includes header and trailer.
 
 #### Unary call
 
-Header and trailer sent along with a unary call can be retrieved using function [Header](https://godoc.org/google.golang.org/grpc#Header) and [Trailer](https://godoc.org/google.golang.org/grpc#Trailer) in [CallOption](https://godoc.org/google.golang.org/grpc#CallOption):
+Header and trailer sent along with a unary call can be retrieved using function [Header](https://godoc.org/github.com/dubbogo/grpc-go#Header) and [Trailer](https://godoc.org/github.com/dubbogo/grpc-go#Trailer) in [CallOption](https://godoc.org/github.com/dubbogo/grpc-go#CallOption):
 
 ```go
 var header, trailer metadata.MD // variable to store header and trailer
@@ -149,7 +149,7 @@ For streaming calls including:
 - Client streaming RPC
 - Bidirectional streaming RPC
 
-Header and trailer can be retrieved from the returned stream using function `Header` and `Trailer` in interface [ClientStream](https://godoc.org/google.golang.org/grpc#ClientStream):
+Header and trailer can be retrieved from the returned stream using function `Header` and `Trailer` in interface [ClientStream](https://godoc.org/github.com/dubbogo/grpc-go#ClientStream):
 
 ```go
 stream, err := client.SomeStreamingRPC(ctx)
@@ -194,7 +194,7 @@ func (s *server) SomeStreamingRPC(stream pb.Service_SomeStreamingRPCServer) erro
 
 #### Unary call
 
-To send header and trailer to client in unary call, the server can call [SendHeader](https://godoc.org/google.golang.org/grpc#SendHeader) and [SetTrailer](https://godoc.org/google.golang.org/grpc#SetTrailer) functions in module [grpc](https://godoc.org/google.golang.org/grpc).
+To send header and trailer to client in unary call, the server can call [SendHeader](https://godoc.org/github.com/dubbogo/grpc-go#SendHeader) and [SetTrailer](https://godoc.org/github.com/dubbogo/grpc-go#SetTrailer) functions in module [grpc](https://godoc.org/github.com/dubbogo/grpc-go).
 These two functions take a context as the first parameter.
 It should be the RPC handler's context or one derived from it:
 
@@ -211,7 +211,7 @@ func (s *server) SomeRPC(ctx context.Context, in *pb.someRequest) (*pb.someRespo
 
 #### Streaming call
 
-For streaming calls, header and trailer can be sent using function `SendHeader` and `SetTrailer` in interface [ServerStream](https://godoc.org/google.golang.org/grpc#ServerStream):
+For streaming calls, header and trailer can be sent using function `SendHeader` and `SetTrailer` in interface [ServerStream](https://godoc.org/github.com/dubbogo/grpc-go#ServerStream):
 
 ```go
 func (s *server) SomeStreamingRPC(stream pb.Service_SomeStreamingRPCServer) error {

Documentation/concurrency.md

@@ -6,7 +6,7 @@ connection will be closed. Note that pings are only necessary when there's no
 activity on the connection.
 
 For how to configure keepalive, see
-https://godoc.org/google.golang.org/grpc/keepalive for the options.
+https://godoc.org/github.com/dubbogo/grpc-go/keepalive for the options.
 
 ## Why do I need this?
 
@@ -22,8 +22,8 @@ Sending pings would make the connections not "idle".
 ## What should I set?
 
 It should be sufficient for most users to set [client
-parameters](https://godoc.org/google.golang.org/grpc/keepalive) as a [dial
-option](https://godoc.org/google.golang.org/grpc#WithKeepaliveParams).
+parameters](https://godoc.org/github.com/dubbogo/grpc-go/keepalive) as a [dial
+option](https://godoc.org/github.com/dubbogo/grpc-go#WithKeepaliveParams).
 
 ## What will happen?
 
@@ -40,13 +40,13 @@ connection during this period (a ping ack is an activity).
 
 Server has similar `Time` and `Timeout` settings as client. Server can also
 configure connection max-age. See [server
-parameters](https://godoc.org/google.golang.org/grpc/keepalive#ServerParameters)
+parameters](https://godoc.org/github.com/dubbogo/grpc-go/keepalive#ServerParameters)
 for details.
 
 ### Enforcement policy
 
 [Enforcement
-policy](https://godoc.org/google.golang.org/grpc/keepalive#EnforcementPolicy) is
+policy](https://godoc.org/github.com/dubbogo/grpc-go/keepalive#EnforcementPolicy) is
 a special setting on server side to protect server from malicious or misbehaving
 clients.
 

Documentation/encoding.md

@@ -12,4 +12,4 @@ connection before giving it to gRPC.
 
 If the default proxy doesn't work for you, replace the default dialer with your
 custom proxy dialer. This can be done using
-[`WithDialer`](https://godoc.org/google.golang.org/grpc#WithDialer).
+[`WithDialer`](https://godoc.org/github.com/dubbogo/grpc-go#WithDialer).

Documentation/grpc-auth-support.md

@@ -58,11 +58,11 @@ receives an error with details:
 exit status 1
 ```
 
-[status]:       https://godoc.org/google.golang.org/grpc/status#Status
-[new-status]:   https://godoc.org/google.golang.org/grpc/status#New
-[code]:         https://godoc.org/google.golang.org/grpc/codes#Code
-[with-details]: https://godoc.org/google.golang.org/grpc/internal/status#Status.WithDetails
-[details]:      https://godoc.org/google.golang.org/grpc/internal/status#Status.Details
-[status-err]:   https://godoc.org/google.golang.org/grpc/internal/status#Status.Err
-[status-error]: https://godoc.org/google.golang.org/grpc/status#Error
+[status]:       https://godoc.org/github.com/dubbogo/grpc-go/status#Status
+[new-status]:   https://godoc.org/github.com/dubbogo/grpc-go/status#New
+[code]:         https://godoc.org/github.com/dubbogo/grpc-go/codes#Code
+[with-details]: https://godoc.org/github.com/dubbogo/grpc-go/internal/status#Status.WithDetails
+[details]:      https://godoc.org/github.com/dubbogo/grpc-go/internal/status#Status.Details
+[status-err]:   https://godoc.org/github.com/dubbogo/grpc-go/internal/status#Status.Err
+[status-error]: https://godoc.org/github.com/dubbogo/grpc-go/status#Error
 [example]:      https://github.com/grpc/grpc-go/tree/master/examples/features/errors

Documentation/grpc-metadata.md

@@ -19,9 +19,9 @@ make the following changes:
 --- a/examples/helloworld/greeter_server/main.go
 +++ b/examples/helloworld/greeter_server/main.go
 @@ -40,6 +40,7 @@ import (
-        "google.golang.org/grpc"
-        pb "google.golang.org/grpc/examples/helloworld/helloworld"
-+       "google.golang.org/grpc/reflection"
+        "github.com/dubbogo/grpc-go"
+        pb "github.com/dubbogo/grpc-go/examples/helloworld/helloworld"
++       "github.com/dubbogo/grpc-go/reflection"
  )
 
  const (

Documentation/keepalive.md

@@ -1,33 +1,33 @@
 all: vet test testrace
 
 build:
-	go build google.golang.org/grpc/...
+	go build github.com/dubbogo/grpc-go/...
 
 clean:
-	go clean -i google.golang.org/grpc/...
+	go clean -i github.com/dubbogo/grpc-go/...
 
 deps:
-	GO111MODULE=on go get -d -v google.golang.org/grpc/...
+	GO111MODULE=on go get -d -v github.com/dubbogo/grpc-go/...
 
 proto:
 	@ if ! which protoc > /dev/null; then \
 		echo "error: protoc not installed" >&2; \
 		exit 1; \
 	fi
-	go generate google.golang.org/grpc/...
+	go generate github.com/dubbogo/grpc-go/...
 
 test:
-	go test -cpu 1,4 -timeout 7m google.golang.org/grpc/...
+	go test -cpu 1,4 -timeout 7m github.com/dubbogo/grpc-go/...
 
 testsubmodule:
-	cd security/advancedtls && go test -cpu 1,4 -timeout 7m google.golang.org/grpc/security/advancedtls/...
-	cd security/authorization && go test -cpu 1,4 -timeout 7m google.golang.org/grpc/security/authorization/...
+	cd security/advancedtls && go test -cpu 1,4 -timeout 7m github.com/dubbogo/grpc-go/security/advancedtls/...
+	cd security/authorization && go test -cpu 1,4 -timeout 7m github.com/dubbogo/grpc-go/security/authorization/...
 
 testrace:
-	go test -race -cpu 1,4 -timeout 7m google.golang.org/grpc/...
+	go test -race -cpu 1,4 -timeout 7m github.com/dubbogo/grpc-go/...
 
 testdeps:
-	GO111MODULE=on go get -d -v -t google.golang.org/grpc/...
+	GO111MODULE=on go get -d -v -t github.com/dubbogo/grpc-go/...
 
 vet: vetdeps
 	./vet.sh