gix integration breaks doc building about cargo HOT 5 CLOSED

There are some nuances between normal cargo build and cargo doc. For each rustc invocation, Cargo requests for dep-info files to deteremine when to rebuild. However, rustdoc doesn't have the equivalent functionality (yet), so the best-effort solution for now is walking through the file system and record the latest file modified time.

See also the Cargo internal doc for fingerprint.

from cargo.

Byron/gitoxide#1371 has been merged. The next step is waiting for a new release, and determine if we want a beta backport before Gitoxide integration hits stable.

from cargo.

The fix for this is in this PR, and it works by adding lenient_config support to all paths gitoxide would encounter. Previously, it would always reject empty paths, but now it will ignore these.

Note that the repository is opened with default options, which uses the lenient_config mode by default. This also means that in its current form, cargo depends on a default value, but it's one that I don't intend to change.

Lastly, I plan to create a new release in the coming week and hope I will do my best to not forget to upgrade gix here.

from cargo.

thanks for the quick response and insights.

one thing is still not clear to me though: I only get this error when I do cargo doc, but other sub commands (check, build, run, fmt, etc.) are not affected at all. I wonder if the doc command triggers this by accident, or is it fundamental different how doc works than the other commands?

from cargo.

Close as #13948 should have resolved this. The new nightly cargo should come out on this Friday/Saturday. Let us know if the issue persists then.

from cargo.