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

Pull rw-stream-sink into this rust-libp2p? #2504

Closed
smoelius opened this issue Feb 10, 2022 · 6 comments · Fixed by #2641
Closed

Pull rw-stream-sink into this rust-libp2p? #2504

smoelius opened this issue Feb 10, 2022 · 6 comments · Fixed by #2641

Comments

@smoelius
Copy link

Should rw-stream-sink be brought into rust-libp2p's workspace?

Doing so would help ensure that rw-stream-sink is regularly linted and tested.

The only potential downside I can see is: it could complicate how you publish libp2p and/or rw-stream-sink.

If this change is considered reasonable, I could submit a PR.

@mxinden
Copy link
Member

mxinden commented Feb 14, 2022

Doing so would help ensure that rw-stream-sink is regularly linted and tested.

Has there been a recent incident that would warrant the move of rw-stream-sink specifically? Are you interested in moving rw-stream-sink only, or all smaller crates? I am having difficulties understanding the concrete motivation here.

@smoelius
Copy link
Author

smoelius commented Feb 14, 2022

Has there been a recent incident ...

No, and I'm sorry for being cryptic.

rw-stream-sink uses an old version of pin-project (^0.4.6). @hamamo opened an issue about this on October 1, but the issue seems to have gone unnoticed. In short, it seems that rw-stream-sink is not getting the attention it deserves. Having rw-stream-sink use the same Cargo.lock file as the other crates in this repository should help with the dependency aspect of this problem. And there would likely be additional benefits, as I alluded to above.

Re other small crates, I think it depends on several factors, such as "who are the crate's consumers?" and "does the crate warrant independent development?" For rw-streak-sink, its primary consumer appears to be libp2p, and it doesn't seemed to have received any independent development. (It has just one commit.)

Again, sorry for appearing out of left field. I hope the question makes more sense now.

@mxinden
Copy link
Member

mxinden commented Feb 16, 2022

I am happy to maintain rw-stream-sink. @tomaka in case you think this is a good idea, i.e. moving rw-stream-sink into rust-libp2p/misc/, can you make me an owner on https://crates.io/crates/rw-stream-sink/?

@mathiversen
Copy link

mathiversen commented Apr 1, 2022

I'm not able to compile the repository locally and it seems to be because of this.
image
image

@smoelius
Copy link
Author

smoelius commented Apr 3, 2022

Hi, @mathiversen. I think this version of pin-project addresses that error: https://github.com/taiki-e/pin-project/releases/tag/v0.4.29

Perhaps cargo update -p pin-project will fix your problem?

@tomaka
Copy link
Member

tomaka commented Apr 19, 2022

can you make me an owner on https://crates.io/crates/rw-stream-sink/?

Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants