Skip to content

merge queue: checking #18 on main (095a625) - #19

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/ebc07857df
Closed

mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/ebc07857df

Conversation

@mergify

@mergify mergify Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

#18 is queued for merge on branch main (095a625).

This pull request has been created by Mergify to check the mergeability of #18.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 095a62559bc291fc42e4aa7639995ccb58418ae5
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 18
    scopes: []
scopes: []
...

mairp and others added 2 commits September 29, 2026 22:41
…eps them

~99% of twin requests are scanners/crawlers (method_not_allowed, forbidden_origin). A Phoenix-only
tail_sampling policy drops those whole traces so real conversations stay visible; Tempo/ClickHouse
and the digital-twin-traces dashboard still count them. Verified through the tunnel: bot reject
2 spans in Tempo / 0 in Phoenix, answered trace in both.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AnNpvt9FGCYPErJvHzyji5
@mergify mergify Bot closed this Sep 29, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/ebc07857df branch September 29, 2026 18:43
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