-
Notifications
You must be signed in to change notification settings - Fork 23
Fix key routes for base64 public keys #244
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
Merged
senamakel
merged 1 commit into
tinyhumansai:main
from
naturedesk:fix/keys-public-key-route-and-bounty-diagnostics
Jul 12, 2026
+149
−13
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Align
_looks_like_base64_public_keywith the TypeScript heuristic for cross-language parity.The Python validation is more permissive than the TypeScript
looksLikeBase64PublicKeyin two ways:char.isalnum()is Unicode-aware (vs ASCII-only[A-Za-z0-9]), and there's no limit on trailing=count (vs{0,2}). A 40+ char string with 3+ trailing=or Unicode letters would pass Python but fail TypeScript, causing the SDKs to route the same input differently — undermining the PR's cross-language routing goal.Using a regex matching the TypeScript implementation closes both gaps:
🔧 Proposed fix for cross-language parity
def _looks_like_base64_public_key(value: str) -> bool: if len(value) < 40 or not any(marker in value for marker in "+/="): return False - return all(char.isalnum() or char in "+/=" for char in value) and ( - value.rstrip("=").count("=") == 0 - ) + import re + return bool(re.fullmatch(r"[A-Za-z0-9+/]+={0,2}", value))Move the
import reto the top of the file if not already present.📝 Committable suggestion
🤖 Prompt for AI Agents