Skip to content

grpc-js: Different handling for errors when starting streams#1251

Merged
murgatroid99 merged 2 commits intogrpc:masterfrom
murgatroid99:grpc-js_handle_call_start_failure
Feb 4, 2020
Merged

grpc-js: Different handling for errors when starting streams#1251
murgatroid99 merged 2 commits intogrpc:masterfrom
murgatroid99:grpc-js_handle_call_start_failure

Conversation

@murgatroid99
Copy link
Copy Markdown
Member

The first few lines of this change are just formatting fixes. The relevant parts are the tryPick changes. This fixes #1250 (see my comment in the issue linked from that issue).

Status.UNAVAILABLE,
'Failed to start call on picked subchannel'
);
/* An error here indicates thaat something when wrong with
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"thaat"

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed it, plus two other errors in that comment.

Copy link
Copy Markdown
Contributor

@nicolasnoble nicolasnoble left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo - otherwise LGTM

@murgatroid99
Copy link
Copy Markdown
Member Author

Windows Node 12 failure: js client -> js server.client should not wait for ready by default. Expected UNAVAILABLE, got DEADLINE_EXCEEDED.

Rerunning to check for consistency. This test does not use the server, so the server language should not matter, but the same test passed with js client -> native server.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Getting strange error regarding subchannels

3 participants