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

Can not handle send error #2

Open
WenceyWang opened this issue Aug 27, 2018 · 2 comments · May be fixed by #11
Open

Can not handle send error #2

WenceyWang opened this issue Aug 27, 2018 · 2 comments · May be fixed by #11

Comments

@WenceyWang
Copy link

WenceyWang commented Aug 27, 2018

******************************************************************************
Starting: Send Telegram Notification
******************************************************************************
==============================================================================
Task         : Telegram Notification
Description  : Send custom message to telegram chat
Version      : 0.1.0
Author       : Evgeny Chernyi
Help         : https://github.com/JackB1ack/telegram-notification
==============================================================================
Message sent!
(node:1884) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): FetchError: request to https://api.telegram.org/**********************************/sendMessage failed, reason: connect ETIMEDOUT *****************:443
******************************************************************************
Finishing: Send Telegram Notification
******************************************************************************
@JackB1ack
Copy link
Owner

Hello Wencey, the task still lacks proxying method, that's why you probably get a timeout error.

@WenceyWang
Copy link
Author

WenceyWang commented Aug 27, 2018

Yes, but this is an error and should report to vsts that this task is failed.

hootanht added a commit to hootanht/telegram-notification that referenced this issue Sep 13, 2024
@hootanht hootanht linked a pull request Sep 13, 2024 that will close this issue
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 a pull request may close this issue.

2 participants