Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove the global allow for deprecated_safe_2024, add an exclusion in mesh #668

Merged
merged 1 commit into from
Jan 14, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -590,7 +590,6 @@ rust_2018_idioms = { level = "deny", priority = -2 }
rust-2024-compatibility = { level = "warn", priority = -1 }
edition_2024_expr_fragment_specifier = "allow"
# TODO: Fix all of the below, https://github.com/microsoft/openvmm/issues/288
deprecated-safe-2024 = "allow"
tail-expr-drop-order = "allow"
if-let-rescope = "allow"

Expand Down
1 change: 1 addition & 0 deletions support/mesh/mesh_process/src/lib.rs
Original file line number Diff line number Diff line change
Expand Up @@ -161,6 +161,7 @@ async fn node_from_environment() -> anyhow::Result<Option<NodeResult>> {
// current edition), either this function and its callers need to become
// `unsafe`, or we need to avoid using the environment to propagate the
// invitation so that we can avoid this call.
#[expect(deprecated_safe_2024)]
std::env::remove_var(INVITATION_ENV_NAME);

let invitation: Invitation = mesh::payload::decode(
Expand Down
Loading