Luca Palmieri

When running `cargo px c`, we invoke the code generators for **all** code-generated crates in the workspace. It'd be nice if `cargo px c --package ` would only invoke the...

It should fix https://github.com/LukeMathWalker/cargo-chef/issues/295 in `cargo-chef`.

[MOD-10008] Reduce the amount of unsafe code by using more idiomatic Rust definitions

2

## Describe the changes in the pull request Correctness is our paramount concern when manipulating C types in Rust. When defining idiomatic Rust wrappers, we are caught between a rock...

[8.2 backport] [MOD-9991] Check security advisories and license compatibility for Rust

3

## Describe the changes in the pull request Backporting #6252 to 8.2. #### Mark if applicable - [ ] This PR introduces API changes - [ ] This PR introduces...

Examples with hidden lines should be editable

5

# Problem For this issue, there are two types of code blocks: - Read-only ones, defined via ` ```rust ` - Editable ones, defined via ` ```rust,editable ` Read-only code...

`cargo-px` honors the `--package`/`-p` flags at the moment (see #39), but it doesn't support `--manifest-path`, `--workspace`/`--exclude` nor `--lib`/`--bin`/etc. We should aim for feature parity with `cargo` in target selection to...

`rustls_platform_verifier::Verifier::new_with_extra_roots`: Improve error clarity for invalid certificates

2

The error returned by `rustls_platform_verifier::Verifier::new_with_extra_roots` doesn't specify _which_ of the provided extra roots was invalid: ```rust pub fn new_with_extra_roots( roots: impl IntoIterator

[PostgreSQL] Must TLS configuration parameters mirror what's available in `libpq`?

5

### I have found these related issues/pull requests - ### Description The current [`PgConfig`](https://docs.rs/sqlx/latest/sqlx/postgres/struct.PgConnectOptions.html) definition seems to mirror quite closely, for TLS, the corresponding options in `libpq`: `sslmode`, `sslrootcert`, `sslcert`,...

### Does your PR solve an issue? Closes #4049. ### Is this a breaking change? No. There is a breaking change for `sqlx-core`, but that's considered [semver-exempt](https://docs.rs/sqlx-core/0.8.6/sqlx_core/#note-semver-exempt-api). ## Open Design...