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

regression: socket type changes #100551

Closed
Mark-Simulacrum opened this issue Aug 14, 2022 · 4 comments
Closed

regression: socket type changes #100551

Mark-Simulacrum opened this issue Aug 14, 2022 · 4 comments
Labels
regression-from-stable-to-beta Performance or correctness regression from stable to beta. relnotes Marks issues that should be documented in the release notes of the next release. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Milestone

Comments

@Mark-Simulacrum
Copy link
Member

Mark-Simulacrum commented Aug 14, 2022

Filing this mostly so that we're aware of scope of impact per Crater run and can potentially use this as a landing ground for complaints/concerns (probably should have some issue for that even if not this one, maybe pinned). The scope of impact is pretty depressing, but I don't think the decision by libs-api will change since this isn't new data, so we'll need to clearly communicate it (I believe already planned into release post + notes). It seems likely that we might want to invest in mechanisms to stop future breakage like this (e.g., more strict linting/errors on transmutes of std types).

introduced by PR #78802

Root (compilation) regressions:

Test failures, which are probably caused by broken pointer casting in older tokio/mio/etc (haven't chased down specifically though), leading to InvalidInput / invalid argument from the kernel:

@Mark-Simulacrum Mark-Simulacrum added T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. regression-from-stable-to-beta Performance or correctness regression from stable to beta. I-libs-api-nominated Nominated for discussion during a libs-api team meeting. labels Aug 14, 2022
@Mark-Simulacrum Mark-Simulacrum added this to the 1.64.0 milestone Aug 14, 2022
@rustbot rustbot added the I-prioritize Issue: Indicates that prioritization has been requested for this issue. label Aug 14, 2022
@estebank
Copy link
Contributor

Have we looped in the tokio/mio people already?

@Mark-Simulacrum
Copy link
Member Author

I think this is all from old versions and yes, but it seems like a good idea to re-check-in, especially since bug reports directed at them aren't implausible.

@joshtriplett
Copy link
Member

We've discussed this pretty extensively in libs-api, and we're comfortable with this change; we do need a release note here, though.

@the8472
Copy link
Member

the8472 commented Aug 17, 2022

The PR is labeled appropriately.

@m-ou-se m-ou-se added relnotes Marks issues that should be documented in the release notes of the next release. and removed I-libs-api-nominated Nominated for discussion during a libs-api team meeting. I-prioritize Issue: Indicates that prioritization has been requested for this issue. labels Sep 13, 2022
@m-ou-se m-ou-se closed this as completed Sep 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression-from-stable-to-beta Performance or correctness regression from stable to beta. relnotes Marks issues that should be documented in the release notes of the next release. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

6 participants