Fix Telegram Push Bug by Encoding # in URLs#1447
Open
simonlee-hello wants to merge 14 commits intoyogeshojha:masterfrom
Open
Fix Telegram Push Bug by Encoding # in URLs#1447simonlee-hello wants to merge 14 commits intoyogeshojha:masterfrom
simonlee-hello wants to merge 14 commits intoyogeshojha:masterfrom
Conversation
Contributor
|
Woohoo @simonlee-hello! 🎉 You've just dropped some hot new code! 🔥 Hang tight while we review this! You rock! 🤘 |
Change workers concurrency.
Change workers concurrency.
http_crawl: declutters url lists before httpx.
…aused by the default value 10.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description: This pull request resolves an issue where the # character in messages was causing Telegram API requests to misinterpret everything after # as a URL fragment (hash), leading to incomplete or incorrect message delivery.
In URLs, the # symbol is used to denote the start of a fragment identifier, so when it appears unencoded in the message content, it causes the Telegram API to truncate or mishandle the message.
Changes:
Applied URL encoding to the message content using urllib.parse.quote to escape special characters like #. This ensures that the entire message, including text after #, is correctly transmitted to Telegram.
Code Before:
Code After:
By URL encoding the message, we ensure that characters like # are safely transmitted, preventing Telegram from misinterpreting them as hash fragments in URLs.