-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
fix bidirectional streaming for grpc #3602
Conversation
This comment has been minimized.
This comment has been minimized.
Any ideas why tests fail? |
@buger something with goreleaser, I go this message:
Not sure what does that means 👀 but the unit test are passing |
Do not think it is related to goreleaser, but I have no idea why this GH comment about failed test is there. |
…:TykTechnologies/tyk into TT-2693-fix-grpc-bidirectional-streaming
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
At this point all the tests passed, but I noticed some unstability on |
/release to release-3 |
1 similar comment
/release to release-3 |
Working on it! Note that it can take a few minutes. |
/release to release-3.2 |
Working on it! Note that it can take a few minutes. |
<!-- Provide a general summary of your changes in the Title above --> ## Description Fix grpc bidirectional streaming functionality ## Related Issue https://tyktech.atlassian.net/browse/TT-2693 ## Motivation and Context fix https://tyktech.atlassian.net/browse/TT-2693 ## How This Has Been Tested The same as reported in the ticket ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If you're unsure about any of these, don't hesitate to ask; we're here to help! --> - [ ] Make sure you are requesting to **pull a topic/feature/bugfix branch** (right side). If pulling from your own fork, don't request your `master`! - [ ] Make sure you are making a pull request against the **`master` branch** (left side). Also, you should start *your branch* off *our latest `master`*. - [ ] My change requires a change to the documentation. - [ ] If you've changed APIs, describe what needs to be updated in the documentation. - [ ] If new config option added, ensure that it can be set via ENV variable - [ ] I have updated the documentation accordingly. - [ ] Modules and vendor dependencies have been updated; run `go mod tidy && go mod vendor` - [ ] When updating library version must provide reason/explanation for this update. - [ ] I have added tests to cover my changes. - [ ] All new and existing tests passed. - [ ] Check your code additions will not fail linting checks: - [ ] `go fmt -s` - [ ] `go vet` (cherry picked from commit c30e12d)
@buger Succesfully merged |
<!-- Provide a general summary of your changes in the Title above --> ## Description Fix grpc bidirectional streaming functionality ## Related Issue https://tyktech.atlassian.net/browse/TT-2693 ## Motivation and Context fix https://tyktech.atlassian.net/browse/TT-2693 ## How This Has Been Tested The same as reported in the ticket ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If you're unsure about any of these, don't hesitate to ask; we're here to help! --> - [ ] Make sure you are requesting to **pull a topic/feature/bugfix branch** (right side). If pulling from your own fork, don't request your `master`! - [ ] Make sure you are making a pull request against the **`master` branch** (left side). Also, you should start *your branch* off *our latest `master`*. - [ ] My change requires a change to the documentation. - [ ] If you've changed APIs, describe what needs to be updated in the documentation. - [ ] If new config option added, ensure that it can be set via ENV variable - [ ] I have updated the documentation accordingly. - [ ] Modules and vendor dependencies have been updated; run `go mod tidy && go mod vendor` - [ ] When updating library version must provide reason/explanation for this update. - [ ] I have added tests to cover my changes. - [ ] All new and existing tests passed. - [ ] Check your code additions will not fail linting checks: - [ ] `go fmt -s` - [ ] `go vet` (cherry picked from commit c30e12d)
@buger Succesfully merged |
Description
Fix grpc bidirectional streaming functionality
Related Issue
https://tyktech.atlassian.net/browse/TT-2693
Motivation and Context
fix https://tyktech.atlassian.net/browse/TT-2693
How This Has Been Tested
The same as reported in the ticket
Screenshots (if appropriate)
Types of changes
Checklist
fork, don't request your
master
!master
branch (left side). Also, you should startyour branch off our latest
master
.go mod tidy && go mod vendor
go fmt -s
go vet