Eric Huss

> If it's not too much trouble, how did you get that backtrace? `RUST_BACKTRACE=1 cargo test` offered no such insight. I used `lldb` on the test executable.

pulldown_cmark does not support detection of bare URLs. That is an extension that GitHub's parser has. On [dingus](https://spec.commonmark.org/dingus/?text=https%3A%2F%2Ffoo.bar%2F_%2FA%20and%20https%3A%2F%2Fbaz.qux%2F_%2FB), you can see that it parses the same as pulldown_cmark. The URLs...

Thanks for the report! That is indeed weird. It looks like this has been fixed in 1.8, which responds with the error: ```Error { code: -1, klass: 26, message: "push_negotiation...

I believe class 26 is `ErrorClass::Callback`, which can be obtained from [`Error::class`](https://docs.rs/git2/latest/git2/struct.Error.html#method.class).

Thanks for the PR! I believe #1918 is already open to address this. Can you give it a try and see how it works for you?

Sure. There is a similar issue, #2832. Cargo would need to use the structured JSON output from libtest (rust-lang/rust#46450), and somehow re-render the output. Unfortunately I don't know of any...

Thanks! I pushed some editorial changes.

Sorry, I'm not sure I am following. Since git2 is using bitflags, for example: ```c unsigned int update_fetchhead : 1, report_unchanged : 1; ``` from what I understand, there isn't...

Yea, I imagine this is more of a problem for Rust than most other languages. I presume most bindings like Python are written in C which don't have this problem....

Yea, good point. Thanks for taking a look!