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

[BACKPORT] #4120: Do not use the tungstenite re-exported from tokio_tungstenite #4128

Conversation

DCNick3
Copy link
Contributor

@DCNick3 DCNick3 commented Dec 8, 2023

Description

Re-exported does not have the TLS fully functional if we only enable it on tokio-tungstenite, so a direct dependency is required

Linked issue

Fixes #4120

Benefits

Checklist

  • make ci pass

…ported from `tokio_tungstenite`

Re-exported does not have the TLS fully functional if we only enable it on `tokio-tungstenite`, so a direct dependency is required

Signed-off-by: Nikita Strygin <[email protected]>
@github-actions github-actions bot added the iroha2-dev The re-implementation of a BFT hyperledger in RUST label Dec 8, 2023
@mversic mversic merged commit 20dcfb8 into hyperledger-iroha:iroha2-stable Dec 8, 2023
3 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
iroha2-dev The re-implementation of a BFT hyperledger in RUST
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants