Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
Grpc
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tci-gateway-module
Grpc
Commits
458b35af
Commit
458b35af
authored
8 years ago
by
Nathaniel Manista
Browse files
Options
Downloads
Patches
Plain Diff
Fix Python server interop spec noncompliance
Also fix spelling mistakes in the spec itself.
parent
01d7dbac
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/interop-test-descriptions.md
+4
-4
4 additions, 4 deletions
doc/interop-test-descriptions.md
src/python/grpcio/tests/interop/methods.py
+5
-4
5 additions, 4 deletions
src/python/grpcio/tests/interop/methods.py
with
9 additions
and
8 deletions
doc/interop-test-descriptions.md
+
4
−
4
View file @
458b35af
...
...
@@ -968,8 +968,8 @@ request payload bodies received.
[
StreamingOutputCall
]:
#streamingoutputcall
Server implements StreamingOutputCall by replying, in order, with one
StreamingOutputCallResponse
s
for each ResponseParameters in
StreamingOutputCallRequest. Each StreamingOutputCallResponse
s
should have a
StreamingOutputCallResponse for each ResponseParameters in
StreamingOutputCallRequest. Each StreamingOutputCallResponse should have a
payload body of size ResponseParameters.size bytes, as specified by its
respective ResponseParameters. After sending all responses, it closes with OK.
...
...
@@ -977,8 +977,8 @@ respective ResponseParameters. After sending all responses, it closes with OK.
[
FullDuplexCall
]:
#fullduplexcall
Server implements FullDuplexCall by replying, in order, with one
StreamingOutputCallResponse
s
for each ResponseParameters in each
StreamingOutputCallRequest. Each StreamingOutputCallResponse
s
should have a
StreamingOutputCallResponse for each ResponseParameters in each
StreamingOutputCallRequest. Each StreamingOutputCallResponse should have a
payload body of size ResponseParameters.size bytes, as specified by its
respective ResponseParameters. After receiving half close and sending all
responses, it closes with OK.
...
...
This diff is collapsed.
Click to expand it.
src/python/grpcio/tests/interop/methods.py
+
5
−
4
View file @
458b35af
...
...
@@ -79,10 +79,11 @@ class TestService(test_pb2.BetaTestServiceServicer):
def
FullDuplexCall
(
self
,
request_iterator
,
context
):
for
request
in
request_iterator
:
yield
messages_pb2
.
StreamingOutputCallResponse
(
payload
=
messages_pb2
.
Payload
(
type
=
request
.
payload
.
type
,
body
=
b
'
\x00
'
*
request
.
response_parameters
[
0
].
size
))
for
response_parameters
in
request
.
response_parameters
:
yield
messages_pb2
.
StreamingOutputCallResponse
(
payload
=
messages_pb2
.
Payload
(
type
=
request
.
payload
.
type
,
body
=
b
'
\x00
'
*
response_parameters
.
size
))
# NOTE(nathaniel): Apparently this is the same as the full-duplex call?
# NOTE(atash): It isn't even called in the interop spec (Oct 22 2015)...
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment