Comparing changes

Previously, in the #6666, the aptly named `cargo lucifer` was suggested for answering resolver questions. Turns out most of these can be answered now, between logging and `cargo tree`. This adds troubleshooting tips to help highlight the use of these commands to answer these questions. Fixes #6666

docs(ref): Highlight commands to answer dep resolution questions Previously, in the #6666, the aptly named `cargo lucifer` was suggested for answering resolver questions. Turns out most of these can be answered now, between logging and `cargo tree`. This adds troubleshooting tips to help highlight the use of these commands to answer these questions. Fixes #6666

1. I linked to the wrong issue 2. I forgot to actually link it

docs(ref): Fix open-semver-range issue link 1. I linked to the wrong issue 2. I forgot to actually link it

chore(deps): update rust crate gix to 0.55.2 [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [gix](https://togithub.com/Byron/gitoxide) | workspace.dependencies | minor | `0.54.1` -> `0.55.2` | --- ### Release Notes <details> <summary>Byron/gitoxide (gix)</summary> ### [`v0.55.2`](https://togithub.com/Byron/gitoxide/releases/tag/gix-v0.55.2): gix v0.55.2 [Compare Source](https://togithub.com/Byron/gitoxide/compare/gix-v0.55.1...gix-v0.55.2) ##### Bug Fixes - bump `gix-transport` version to prevent it from being picked up. `gix-transport` v0.37.1 could accidentally be picked up by older, incompatible, `gix` versions which now fail to build. Thus v0.37.1 is now yanked and replaced with v0.38.0 along with a new release of `gix` to go with it. ##### Commit Statistics - 2 commits contributed to the release. - 1 commit was understood as [conventional](https://www.conventionalcommits.org). - 0 issues like '(#ID)' were seen in commit messages ##### Commit Details <csr-read-only-do-not-edit/> <details><summary>view details</summary> - **Uncategorized** - Prepare changelogs prior to release ([`12b5caf`](https://togithub.com/Byron/gitoxide/commit/12b5caf)) - Bump `gix-transport` version to prevent it from being picked up. ([`8011c73`](https://togithub.com/Byron/gitoxide/commit/8011c73)) </details> ### [`v0.55.1`](https://togithub.com/Byron/gitoxide/releases/tag/gix-v0.55.1): gix v0.55.1 [Compare Source](https://togithub.com/Byron/gitoxide/compare/gix-v0.55.0...gix-v0.55.1) ##### New Features - Add `take_data()` to all primitive object types. That is the new, most direct way to obtain its data which otherwise is immovable. - Add `detach()` and `detached()` too all object types. That way, the detachment API is symmetric. It's required to overcome the `Drop` implementation of each of these types which prevents moving data out of the object (easily). ##### Commit Statistics - 2 commits contributed to the release. - 2 commits were understood as [conventional](https://www.conventionalcommits.org). - 0 issues like '(#ID)' were seen in commit messages ##### Commit Details <csr-read-only-do-not-edit/> <details><summary>view details</summary> - **Uncategorized** - Add `take_data()` to all primitive object types. ([`5732303`](https://togithub.com/Byron/gitoxide/commit/5732303)) - Add `detach()` and `detached()` too all object types. ([`88f2e6c`](https://togithub.com/Byron/gitoxide/commit/88f2e6c)) </details> ### [`v0.55.0`](https://togithub.com/Byron/gitoxide/releases/tag/gix-v0.55.0): gix v0.55.0 [Compare Source](https://togithub.com/Byron/gitoxide/compare/gix-v0.54.1...gix-v0.55.0) This release contains a complete rewrite of the internal url parsing logic, the public interface stays mostly the same however. Gitoxide will now be more correct, interpreting more urls the same way Git does. Improvements include the added support for ssh aliases (`github:byron/gitoxide` has previously been parsed as local path), adjustments around the interpretation of colons in file names (previously we disallowed colons that were not followed up with a slash character) and some smaller changes that bring the interpretation of file urls more in line with Git's implementation. Additionally, the error types have been adjusted to print a more comprehensive message by default, making sure they stay helpful even when bubbled up through multiple abstraction layers. There are still many (edge) cases in Git's url parsing implementation which are not handled correctly by Gitoxide. If you notice any such deviation please open a new issue to help us making Gitoxide even more correct. ##### Other - <csr-id-f478a3722f0be35c109ea60b79cd4ac6e607480b/> inform about the absence of strict hash verification and strict object creation. Those are present in `git2` and enabled by default, and `gitoxde` definitely wants to do the same at some point. ##### New Features - add `Repository::head_tree()` to more easily obtain the current tree. - Add `Repository::has_object()` as a high-level alternative. Previously, one would have to call `repo.objects.contains()`, which is fine, but this method is necessary for symmetry of the API and one shouldn't have to drop down a level to do this. This method also knows empty trees as special case. - add `Object::try_into_blob()` and `into_blob()` and `Repository::empty_blob()` This way it's easier to assert that an object is actually a blob. - add `Repository::index_or_empty()`. This is useful if a missing index should mean it's empty. ##### Commit Statistics - 14 commits contributed to the release over the course of 16 calendar days. - 17 days passed between releases. - 5 commits were understood as [conventional](https://www.conventionalcommits.org). - 0 issues like '(#ID)' were seen in commit messages ##### Thanks Clippy [Clippy](https://togithub.com/rust-lang/rust-clippy) helped 1 time to make code idiomatic. ##### Commit Details <csr-read-only-do-not-edit/> <details><summary>view details</summary> - **Uncategorized** - Release gix-hash v0.13.1, gix-features v0.36.0, gix-actor v0.28.0, gix-object v0.38.0, gix-glob v0.14.0, gix-attributes v0.20.0, gix-command v0.2.10, gix-filter v0.6.0, gix-fs v0.8.0, gix-commitgraph v0.22.0, gix-revwalk v0.9.0, gix-traverse v0.34.0, gix-worktree-stream v0.6.0, gix-archive v0.6.0, gix-tempfile v11.0.0, gix-lock v11.0.0, gix-ref v0.38.0, gix-config v0.31.0, gix-url v0.25.0, gix-credentials v0.21.0, gix-diff v0.37.0, gix-discover v0.26.0, gix-ignore v0.9.0, gix-index v0.26.0, gix-mailmap v0.20.0, gix-negotiate v0.9.0, gix-pack v0.44.0, gix-odb v0.54.0, gix-pathspec v0.4.0, gix-packetline v0.16.7, gix-transport v0.37.0, gix-protocol v0.41.0, gix-revision v0.23.0, gix-refspec v0.19.0, gix-worktree v0.27.0, gix-status v0.2.0, gix-submodule v0.5.0, gix-worktree-state v0.4.0, gix v0.55.0, safety bump 37 crates ([`68e5432`](https://togithub.com/Byron/gitoxide/commit/68e5432)) - Prepare changelogs prior to release ([`1347a54`](https://togithub.com/Byron/gitoxide/commit/1347a54)) - Merge branch 'improvements' ([`429e7b2`](https://togithub.com/Byron/gitoxide/commit/429e7b2)) - Inform about the absence of strict hash verification and strict object creation. ([`f478a37`](https://togithub.com/Byron/gitoxide/commit/f478a37)) - Add `Repository::head_tree()` to more easily obtain the current tree. ([`c79a7da`](https://togithub.com/Byron/gitoxide/commit/c79a7da)) - Add `Repository::has_object()` as a high-level alternative. ([`787a9aa`](https://togithub.com/Byron/gitoxide/commit/787a9aa)) - Add `Object::try_into_blob()` and `into_blob()` and `Repository::empty_blob()` ([`3cec935`](https://togithub.com/Byron/gitoxide/commit/3cec935)) - Thanks clippy ([`345712d`](https://togithub.com/Byron/gitoxide/commit/345712d)) - Merge branch 'reset' ([`b842691`](https://togithub.com/Byron/gitoxide/commit/b842691)) - Trust Ctime again ([`f929d42`](https://togithub.com/Byron/gitoxide/commit/f929d42)) - Add `Repository::index_or_empty()`. ([`7d9ecdd`](https://togithub.com/Byron/gitoxide/commit/7d9ecdd)) - Adapt to changes in `gix-status` ([`54fb7c2`](https://togithub.com/Byron/gitoxide/commit/54fb7c2)) - Merge branch 'gix-url-parse-rewrite' ([`a12e4a8`](https://togithub.com/Byron/gitoxide/commit/a12e4a8)) - Update changelogs ([`4349353`](https://togithub.com/Byron/gitoxide/commit/4349353)) </details> </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 5am on the first day of the month" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/rust-lang/cargo).

Add regression test for issue 6915: features and transitive dev deps Closes #6915. That issue was fixed without realizing by #10103. In search of test coverage, I looked through `rg '[a-z0-9_-]+ = \["[a-z0-9_-]+/[a-z0-9_-]+"\]' tests/testsuite/` and did not find any existing test that exercises this situation. The tests added by #10103 are focused on cycles and `cargo tree`, which is substantially different from #6915. Tested by `cargo test --test testsuite -- features::activating_feature_does_not_activate_transitive_dev_dependency`.

This demonstrate the buggy behavior that profile merge on `trim-paths` doesn't work as expected.

In 4d29af1 we forgot to add trim-paths to `fn merge()`. This commit follows how `-Zprofile-rustflags` works --- overriding instead of merging array.

fix: merge `trim-paths` from different profiles

Updating docs to reflect the fact that crate features are limited to 300 to ensure system stability as per this blog post announcement: https://blog.rust-lang.org/2023/10/26/broken-badges-and-23k-keywords.html

Update features.md

Updating "features" documentation to add a note about the new limit on number of features ### What does this PR try to resolve? Adding the following note to [features docs page](https://doc.rust-lang.org/cargo/reference/features.html) > Note: New crates or versions published on [crates.io](http://crates.io/) are now limited to > a maximum of 300 features. Exceptions are granted on a case-by-case basis. > See this [blog post] for details. Participation in solution discussions is > encouraged via the [crates.io](http://crates.io/) Zulip stream. ### How should we test and review this PR? I don't think this change requires any additional testing beyond a general review. ### Additional information

We already refer to test targets as "test targets" instead of "tests" in `--test` but not `--tests` or in the error output. This makes it uniformly refer to them as "test targets", making it clearer that these aren't test functions. Fixes #7864

fix(cli): Clarify --test is for targets, not test functions We already refer to test targets as "test targets" instead of "tests" in `--test` but not `--tests` or in the error output. This makes it uniformly refer to them as "test targets", making it clearer that these aren't test functions. Fixes #7864

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Comparing changes

Open a pull request

Commits on Oct 31, 2023

Commits on Nov 1, 2023

Commits on Nov 2, 2023

Commits on Nov 3, 2023

This comparison is taking too long to generate.

Uh oh!