ack 1b154bb

I believe I addressed each suggestion. If I missed anything just let me know. As #433 , this is also being prevented to build doc as the bitcoin_hashes dependency is failing to build docs.

As #433 , this is also being prevented to build doc as the bitcoin_hashes dependency is failing to build docs.

Oh, shoot! rustc is panic-ing while trying to build docs for this crate. Is that new?

(We should run cargo docs on our CI too 🤔)

As #433 , this is also being prevented to build doc as the bitcoin_hashes dependency is failing to build docs.

Oh, shoot! rustc is panic-ing while trying to build docs for this crate. Is that new?

(We should run cargo docs on our CI too 🤔)

Well, it was working about 10 days ago as I was able to create the docs. I ran cargo doc --open without an issue on Rust-Bitcoin. I am checking now to see whats really going on.

This is the log am I getting:

query stack during panic:
 Documenting futures-executor v0.3.31
#0 [doc_link_resolutions] resolutions for documentation links for a module
end of query stack
error: could not document `bitcoin_hashes`

I know @luisschwab also got this same error, is anyone else getting it when running cargo doc --open?

This is the log am I getting:

query stack during panic:
 Documenting futures-executor v0.3.31
#0 [doc_link_resolutions] resolutions for documentation links for a module
end of query stack
error: could not document `bitcoin_hashes`

I know @luisschwab also got this same error, is anyone else getting it when running cargo doc --open?

I was... maybe we could raise this for the bitcoin_hashes folks ?

This is the log am I getting:

query stack during panic:

Documenting futures-executor v0.3.31

#0 [doc_link_resolutions] resolutions for documentation links for a module

end of query stack

error: could not document bitcoin_hashes

I know @luisschwab also got this same error, is anyone else getting it when running cargo doc --open?

I was... maybe we could raise this for the bitcoin_hashes folks ?

I tried to build the Bitcoin Rust docs to see if anything would happen. It didn't. It appears to be a problem when it's on dependencies.