Skip to content

feat: use warn_log_format for discarded messages #21053

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.

Sign up for GitHub

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

Merged
nchamo merged 1 commit into from
Mar 3, 2026
Merged

feat: use warn_log_format for discarded messages #21053

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions noir-projects/aztec-nr/aztec/src/messages/discovery/process_message.nr
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ use crate::messages::{
processing::MessageContext,
};

use crate::protocol::{address::AztecAddress, logging::{debug_log, debug_log_format}};
use crate::protocol::{address::AztecAddress, logging::{debug_log, warn_log_format}};

/// Processes a message that can contain notes, partial notes, or events.
///
Expand Down Expand Up @@ -43,7 +43,7 @@ pub unconstrained fn process_message_ciphertext<ComputeNoteHashAndNullifierEnv,
message_context,
);
} else {
debug_log_format(
warn_log_format(
"Could not decrypt message ciphertext from tx {0}, ignoring",
[message_context.tx_hash],
);
Expand Down Expand Up @@ -99,7 +99,7 @@ pub(crate) unconstrained fn process_message_plaintext<ComputeNoteHashAndNullifie
// The message type ID falls in the range reserved for aztec.nr built-in types but wasn't matched above. This
// most likely means the message is malformed or a custom message was incorrectly assigned a reserved ID.
// Custom message types must use IDs allocated via `custom_msg_type_id`.
debug_log_format(
warn_log_format(
"Message type ID {0} is in the reserved range but is not recognized, ignoring. See https://docs.aztec.network/errors/3",
[msg_type_id as Field],
);
Expand All @@ -114,7 +114,7 @@ pub(crate) unconstrained fn process_message_plaintext<ComputeNoteHashAndNullifie
} else {
// A custom message was received but no handler is configured. This likely means the contract emits custom
// messages but forgot to register a handler via `AztecConfig::custom_message_handler`.
debug_log_format(
warn_log_format(
"Received custom message with type id {0} but no handler is configured, ignoring. See https://docs.aztec.network/errors/2",
[msg_type_id as Field],
);
Expand Down
Loading