Skip to content
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

v1.44.0 gRPC client support doesn't work #24058

Closed
rnbguy opened this issue May 31, 2024 · 0 comments · Fixed by #24147
Closed

v1.44.0 gRPC client support doesn't work #24058

rnbguy opened this issue May 31, 2024 · 0 comments · Fixed by #24147
Assignees
Labels
bug Something isn't working correctly node compat

Comments

@rnbguy
Copy link
Contributor

rnbguy commented May 31, 2024

Version: Deno v1.44.0

I opened this issue because of this comment: #3326 (comment)

We have a NPM executable that connects to a gRPC server. The current gRPC support doesn't work with it.

You can reproduce this by doing the following:

git clone https://github.com/informalsystems/quint
cd quint/examples/cosmos/ics20
deno run -A npm:@informalsystems/quint verify --max-steps=3 --main=bankTests --invariant=BalanceNonNegative,NonExistantAccountsOrCoinsAreZero bank.qnt

I get the following error:

Warning: Not implemented: Http2Session.socket
Warning: Not implemented: Http2Session.socket

Internally, @informalsystems/quint downloads apalache and executes apalache server that launchs the gRPC server and then quint tries to connect to it via @grpc/grpc-js.

The source code for the gRPC client lives at https://github.com/informalsystems/quint/blob/main/quint/src/apalache.ts.

Am I doing anything wrong?

PS. to minimize the debugging overhead, you can just use apalache and this Deno script: https://gist.github.com/rnbguy/77e73b3ea9515f8013a66060acb9796f.

In two different terminals:

apalache server
deno run ping_apalache.ts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working correctly node compat
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants