Skip to content
This repository was archived by the owner on Nov 6, 2020. It is now read-only.

IPC endpoint gets into invalid state when accessed concurrently #5470

Closed
dstarcev opened this issue Apr 18, 2017 · 2 comments
Closed

IPC endpoint gets into invalid state when accessed concurrently #5470

dstarcev opened this issue Apr 18, 2017 · 2 comments
Assignees
@NikVolf
Labels
F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust.
Milestone
1.8

Comments

@dstarcev
Copy link
Contributor

IPC endpoint seems to get broken when there are more than two connections to it.
I have written a small script that helps to reproduce the bug by sending requests from 5 concurrent connections and printing how many of them succeed.
https://github.com/dstarcev/parity-ipc-killer
@5chdn 5chdn added F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust. labels Apr 19, 2017
@NikVolf NikVolf self-assigned this Apr 19, 2017
@NikVolf
Copy link
Contributor

NikVolf commented Apr 19, 2017

The fix will require synchronizing api of two libs (tokio-uds/tokio-named-pipes) and will take some (hopefully short) time

@NikVolf NikVolf mentioned this issue Apr 21, 2017
Merged
@5chdn 5chdn added this to the 1.7 milestone May 9, 2017
@5chdn
Copy link
Contributor

5chdn commented May 9, 2017 •
edited
Loading

This issue is labelled with bug: The client fails to follow expected behavior. It's assigned to @NikVolf but not linked to a milestone.

I'm closing this as fixed as a patch is available in #5489 and attaching it to milestone 1.7. Please reopen if this issue still persists.

@5chdn 5chdn closed this as completed May 9, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@NikVolf NikVolf

Labels
F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust.
Projects
None yet
Milestone
1.8
Development

No branches or pull requests
3 participants
@dstarcev @NikVolf @5chdn