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

The link to BigUInt fails. #2673

Open
piaoyh opened this issue Nov 16, 2024 · 2 comments
Open

The link to BigUInt fails. #2673

piaoyh opened this issue Nov 16, 2024 · 2 comments

Comments

@piaoyh
Copy link

piaoyh commented Nov 16, 2024

Crate name

cryptocol

Build failure link

https://docs.rs/cryptocol/0.8.5-fix.1/cryptocol/number/big_uint/struct.BigUInt.html#struct.BigUInt

Requested RAM limit

No response

Requested timeout

No response

Requested number of targets

No response

Why your crate needs the resource increases

So far, I haven't had any problem to publish my crate cryptocol. But from version 0.8.5 on, I have a problem in the published documents. In the documents on the website (https://docs.rs/cryptocol/0.8.5-fix.1/cryptocol/index.html), the link to the page of struct BigUInt (for example, https://docs.rs/cryptocol/0.8.5-fix.1/cryptocol/number/big_uint/struct.BigUInt.html#struct.BigUInt) fails. Other links such as SmallUInt (https://docs.rs/cryptocol/0.8.5-fix.1/cryptocol/number/small_uint/trait.SmallUInt.html#trait.SmallUInt) work fine in the documents on the same website.

When I compiled the documentation by "cargo doc" on my local machine, I found that the compilation of documents were successful and all the link including the link to BigUInt in the documents worked fine. However, it does not work only on website. Can you please check whether or not my crate cryptocol reaches the limitation? If the reason why the link fails is due to the server, please fix it. If the reason is in my documentation, please let me know how to fix it.
Thank you in advance.

@syphar
Copy link
Member

syphar commented Nov 18, 2024

hi,

thank you for the report, I couldn't dig into this yet, as to why the links don't work.

In the past these kind of issues were mostly a problem in the crate itself, and only sometimes an issue with cross crate links.

@piaoyh
Copy link
Author

piaoyh commented Nov 21, 2024

Please read the post #2676. I wrote the problem in far more detail.

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

2 participants