Skip to content

fix(relay): log ambiguous workflow @mentions instead of dropping silently (#4436) - #4506

Open
chessing234 wants to merge 4 commits into
block:mainfrom
chessing234:fix/ambiguous-mention-warn-4436
Open

chessing234 wants to merge 4 commits into
block:mainfrom
chessing234:fix/ambiguous-mention-warn-4436

Conversation

@chessing234

@chessing234 chessing234 commented Aug 3, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Test plan

  • cargo test -p buzz-relay --lib workflow_sink::tests
  • Trigger a workflow send_message with @Fizz when two members share that name; relay logs the warn and still posts the message without a Fizz p tag

Dropping the p tag is intentional, but silence made healthy sends look
like dead agents (block#4436). Return matched ambiguous names and log them.

Signed-off-by: Taksh <[email protected]>
Ensure a second @fizz in the same workflow text does not duplicate the
ambiguous-name signal.

Signed-off-by: Taksh <[email protected]>
@chessing234

Copy link
Copy Markdown
Contributor Author

note: #3991 extracts this resolver into buzz-core for desktop typed mentions — if that lands first i'll rebase the warn onto the shared helper.

…on-warn-4436

Signed-off-by: Taksh <[email protected]>

# Conflicts:
#	crates/buzz-relay/src/workflow_sink.rs
@github-actions

github-actions Bot commented Sep 1, 2026 •

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

The current range is d839d3731a11ab363a69e7f5b851c3031b7680dd...fb6bc207d6bab0fdfcd0370db627066d8f5081ae.
A new review must complete for this exact range. When manual authorization
is required, a user with write access must comment exactly
@buzz-security-review fb6bc207d6bab0fdfcd0370db627066d8f5081ae to authorize a new review.
Any previous review applies only to its recorded range.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant