We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The following cases are untested, and should be tested:
grpc-go/internal/transport/http2_client.go
Lines 275 to 278 in fb6867e
Lines 279 to 282 in fb6867e
Lines 298 to 301 in fb6867e
Lines 304 to 307 in fb6867e
e.g. changes in #2219 were almost merged that should not have because of lack of the aforementioned test coverage.
The text was updated successfully, but these errors were encountered:
@ginayeh I would like to contribute here
Sorry, something went wrong.
Sure! Assigning it to you.
The original issue description might not be relevant anymore. I would re-evaluate the missed coverage of the file here.
@v-sreejith -- ping.. Are you still actively tracking this?
No branches or pull requests
The following cases are untested, and should be tested:
grpc-go/internal/transport/http2_client.go
Lines 275 to 278 in fb6867e
grpc-go/internal/transport/http2_client.go
Lines 279 to 282 in fb6867e
grpc-go/internal/transport/http2_client.go
Lines 298 to 301 in fb6867e
grpc-go/internal/transport/http2_client.go
Lines 304 to 307 in fb6867e
e.g. changes in #2219 were almost merged that should not have because of lack of the aforementioned test coverage.
The text was updated successfully, but these errors were encountered: