Skip to content

Documentation for x86_64-unknown-linux-gnu is missing from docs.rs #562

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

Open
proski opened this issue Feb 28, 2025 · 2 comments
Open

Documentation for x86_64-unknown-linux-gnu is missing from docs.rs #562

proski opened this issue Feb 28, 2025 · 2 comments

Comments

@proski
Copy link
Contributor

proski commented Feb 28, 2025

The current documentation on docs.rs is missing the x86_64-unknown-linux-gnu platform: https://docs.rs/socket2/0.5.8/socket2/

The documentation build logs can be seen at https://docs.rs/crate/socket2/0.5.8/builds

Key takeaways:

A new documentation build was run on 2025-02-22. An older build for the same version 0.5.8 was run on 2024-11-27.

Both builds include 11 platforms. Cargo.toml lists 14 platforms as targets for documentation. The most recent build is missing x86_64-unknown-linux-gnu, the older build has that platform but is missing other platforms.

I don't see any information that docs.rs is limited to 11 platforms. But there is a very old mention that it's limited to 10 platforms: rust-windowing/winit#1028 (comment)

@proski proski changed the title Documentation for x86_64-unknown-linux-gnus missing from docs.rs Documentation for x86_64-unknown-linux-gnu is missing from docs.rs Feb 28, 2025
@proski
Copy link
Contributor Author

proski commented Feb 28, 2025

The docs.rs build status page https://docs.rs/crate/socket2/0.5.8/builds is showing at the end:

Maximum number of build targets | 10
If a build fails because it hit one of those limits please open an issue to get them increased.

I assume the are 11 targets because the default target is exempt from the limit.

I guess a ticket to increase the number of build targets needs to be opened by following the link of that page.

@proski
Copy link
Contributor Author

proski commented Mar 4, 2025

Perhaps some targets could be removed from Cargo.toml. For instance, x86_64-unknown-linux-musl only differs from other targets by internal implementation details in the private into_timeval function and in the private IovLen type.

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

No branches or pull requests

1 participant