Skip to content
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

Display unsupported messages correctly #311

Merged

Conversation

LinqLover
Copy link
Contributor

Make sure unsupported messages are displayed even if the chat is already open when they arrive.

Fixes #306.

Make sure unsupported messages are displayed even if the chat is already open when they arrive.
@LinqLover LinqLover added the bugfix Fixes a bug label Oct 7, 2020
@LinqLover
Copy link
Contributor Author

Apparently, there are no tests for the patched class TCCChatsHandler, so I won't add a regression test unless you deem this necessary.

LinqLover added a commit to LinqLover/TelegramBot that referenced this pull request Oct 8, 2020
LinqLover added a commit to LinqLover/TelegramBot that referenced this pull request Oct 12, 2020
- Add GitHub Action workflow (`.github/workflows/main.yml`) to run tests using smalltalkCI (`.smalltalk.ston`)
- Make integration tests CI-ready by providing:
  * secret variables for bot and client (they also have been defined in the [repository settings](https://github.com/LinqLover/TelegramBot/settings/secrets))
  * a test database for TelegramClient (see `assets/tests/tdlib.zip.gpg`) that works out of the box without using a new authentication code. It is encrypted using another secret variable.
  * revising the `TelegramBotIntegrationTest` running logic to make it more robust and fail-safe
- Fix baseline and specify missing dependencies
  * Create an extra package (`TelegramBot-Support-ShoutAttribute`) for extensions depending on the not-yet-released `ShoutAttribute` changeset (4680c53)
  * Add `BaselineOfTelegramBot >> #installPreviewDependencies` to install other not-yet-released proposals for the Squeak Trunk (works around Metacello/metacello#528 and Metacello/metacello#530)
  * Depend on [fork](https://github.com/LinqLover/TelegramClient) of [TelegramClient](https://github.com/hpi-swa-teaching/TelegramClient) until hpi-swa-teaching/TelegramClient#311, hpi-swa-teaching/TelegramClient#312 have been merged (528ae9a)
  * Add missing and remove superfluous extension methods
- API: Revise offset computation for getUpdates method (89c79a0)
- Fix `TelegramBotRequest >> #testSendAudio` (305755e)
- Add badges to `README.md` (7621356)
@LinqLover
Copy link
Contributor Author

Great, thank you for reviewing all these PRs!

@LinqLover LinqLover merged commit ae9fff2 into hpi-swa-teaching:master Oct 22, 2020
@LinqLover LinqLover deleted the fix-unsupported-messages branch October 22, 2020 08:38
LinqLover added a commit to LinqLover/TelegramBot that referenced this pull request Mar 22, 2021
When sending a message from the bot failed because the recipient has blocked the bot, no longer get stuck in the central update cycle by raising one TelegramBotError(403) after the other, but instead raise a dedicated TelegramBotFailure and proceed with the next update. Subclasses can refine the handling of blocked messages by overriding the hook #messageBlocked:withError:. Also introduced a new fancy Abort exception. 🤓

Fixes #17. Tests are included as well.

Also reverts baseline workaround solution from 528ae9a (hpi-swa-teaching/TelegramClient#311 and hpi-swa-teaching/TelegramClient#312 are merged now).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Fixes a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Message of unsupported types only appear if the client is restarted
2 participants