You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is the same problem of the posts #2676 and #2673.
I tried to make a off-line documentation as follows: $ cargo doc
It successfully create the documentation, for example, at /home/youngho/shared/rust-target/doc. It shows some warnings but I found that they are minor and irrelevant to this problems.
When I open the /home/youngho/shared/rust-target/doc/cryptocol/index.html with web browser, it is shown as follows:
And then, I scrolled down and clicked the link BigUInt as follows:
Then, the browser successfully shows the corresponding linked webpage as follows:
However, after I published the same crate to crates.io, if you follow the steps I showed at the post #2676, you will find that the corresponding linked webpage is not shown. It only shows as follows:
It does not have any cross crate link at all and the offline documentation made with the cargo package manager works fine at switching to the linked webpage .
The cargo package manager generates documentation correctly but the server does not generates documentation as the cargo package manager does.
It means that the link to the webpage of BigUInt is correct but the server fails in generating the corresponding linked webpage.
Please recognize that the server does not generate the documentation webpages as the cargo package manager does. They works differently. Please seriously dig it or, at least, report this problem to the team of crates.io developers.
Merry Christmas!
The text was updated successfully, but these errors were encountered:
Crate name
cryptocol
Build failure link
https://docs.rs/cryptocol/latest/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
It is the same problem of the posts #2676 and #2673.
I tried to make a off-line documentation as follows:
$ cargo doc
It successfully create the documentation, for example, at
/home/youngho/shared/rust-target/doc
. It shows some warnings but I found that they are minor and irrelevant to this problems.When I open the
/home/youngho/shared/rust-target/doc/cryptocol/index.html
with web browser, it is shown as follows:And then, I scrolled down and clicked the link BigUInt as follows:
Then, the browser successfully shows the corresponding linked webpage as follows:

However, after I published the same crate to crates.io, if you follow the steps I showed at the post #2676, you will find that the corresponding linked webpage is not shown. It only shows as follows:
It does not have any cross crate link at all and the offline documentation made with the cargo package manager works fine at switching to the linked webpage .
The cargo package manager generates documentation correctly but the server does not generates documentation as the cargo package manager does.
It means that the link to the webpage of BigUInt is correct but the server fails in generating the corresponding linked webpage.
Please recognize that the server does not generate the documentation webpages as the cargo package manager does. They works differently. Please seriously dig it or, at least, report this problem to the team of crates.io developers.
Merry Christmas!
The text was updated successfully, but these errors were encountered: