Skip to content

Fix token pattern to accept organization IDs for API keys#1980

Merged
Viicos merged 2 commits into
mainfrom
vp/fix-token-pattern
May 28, 2026
Merged

Fix token pattern to accept organization IDs for API keys#1980
Viicos merged 2 commits into
mainfrom
vp/fix-token-pattern

Conversation

@Viicos
Copy link
Copy Markdown
Member

@Viicos Viicos commented May 28, 2026

No description provided.

@Viicos Viicos enabled auto-merge (squash) May 28, 2026 15:18
@jirikuncar jirikuncar added the bug Bug related to the Logfire Python SDK label May 28, 2026
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 1 file

Confidence score: 4/5

  • This PR is likely safe to merge, but there is a moderate parsing edge case in logfire/_internal/auth.py that keeps this from a top confidence score.
  • The UUID matcher appears lowercase-only; uppercase hexadecimal UUID text can be rejected, which can incorrectly trigger region parsing fallback to US and affect auth routing behavior.
  • Because the issue is a single, localized validation rule (severity 5/10, confidence 6/10), risk looks limited and straightforward to fix.
  • Pay close attention to logfire/_internal/auth.py - UUID parsing should accept both uppercase and lowercase hex to avoid incorrect region fallback.

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread logfire/_internal/auth.py
@Viicos Viicos merged commit bf62cde into main May 28, 2026
22 checks passed
@Viicos Viicos deleted the vp/fix-token-pattern branch May 28, 2026 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Bug related to the Logfire Python SDK

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants