From: Ammar Faizi <[email protected]>
To: Muhammad Rizki <[email protected]>
Cc: Ammar Faizi <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
Alviro Iskandar Setiawan <[email protected]>
Subject: Re: [PATCH v4 00/17] Fix, improvement and implement a bot logger.
Date: Sun, 25 Dec 2022 03:54:25 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
From: Ammar Faizi <[email protected]>
On Wed, 21 Dec 2022 08:33:30 +0700, Muhammad Rizki wrote:
> This is a v4 revision of fix, improvement and implement a bot logger.
> this series is to improve create_template() caption substr/trim,
> prepare_patch() for the .patch file payload, remove unrelevant changelog
> commit in the commit description, use html.escape() once instead of
> twice, small change in the first commit to make it clearer.
>
> This series contains fixes in the utility file and some improvement for
> it. I also implement a bot logger to log an error to the terminal and
> to the log file, if error may happen it will send the log file to the
> log channel either for Discord or Telegram, the LOG_CHANNEL_ID is
> declared in the config.py.example, copy the channel ID from the Discord
> or Telegram channel and then paste to the config.py.example.
>
> [...]
Applied, thanks!
[01/17] discord: Fix typo on _flood_exception()
commit: b58e0f7517a009cc212b467bf19156363c6e591e
[02/17] utils: Fix .patch file payload
commit: ad154f246b31488fb4cd104c0c1464e215d08f72
[03/17] utils: add a substr for the patch media caption
commit: 82edf7de491b18104c2f055388dcd989044cda0b
[04/17] utils: Fix the extract_list() utility function
commit: 97e8352ad0b6163ffad33ff1eba5059c234dfa53
[05/17] utils: Back to use decode=True for the get_payload()
commit: 087e1ac70426fff0855027408babec6cba06d2b8
[06/17] utils: Improve fix_utf8_char()
commit: 97b217113d3802004a49dfde7e25a5c5aaafce74
[07/17] utils: Add catch_err() for the log message
commit: f24336d484e17b04dafd0b0c9377482908e45fa2
[08/17] logger: Initial work for the bot logger for future use
commit: 5a377dcb2ae2b0d71c373dcabf66b69d6d07dfdd
[09/17] telegram: Use the created BotLogger() class
commit: bd20b32fab4f34112723a5ce348abbaeedbae40b
[10/17] telegram: Add variable LOG_CHANNEL_ID declaration
commit: f1c4f54f7dbb460427538d5f491b9a87f15d80d0
[11/17] telegram: Add send_log_file() in the DaemonClient()
commit: 5d67dc4b1085f472b8621c3b8bcda6f8eef907ce
[12/17] telegram: Implement the log message for catching errors
commit: ce17f3e8016ca72a34a68bbe89edd0a3fa14d1b3
[13/17] discord: Add variable LOG_CHANNEL_ID declaration
commit: 3749c653f7eb71a9e6783149e9c21244587446ae
[14/17] discord: Use the BotLogger() to the GWClient()
commit: fe798886e189885d6e8f3d67e9c24d49cf1a0a88
[15/17] discord: Add send_log_file in the GWClient()
commit: 9448095a77af095f36403c260f89dee0b694d172
[16/17] discord: Implement the catch erros and logs
commit: f7d88b1a831c65e408e170d48a5b9dd5e2cca577
[17/17] Remove some unused imports
commit: 16d7f9acc52518bf3d6410d736673d3759ade3dc
Best regards,
--
Ammar Faizi
next prev parent reply other threads:[~2022-12-24 20:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 1:33 [PATCH v4 00/17] Fix, improvement and implement a bot logger Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 01/17] discord: Fix typo on _flood_exception() Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 02/17] fix: utils: Fix .patch file payload Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 03/17] fix: utils: add a substr for the patch media caption Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 04/17] fix: utils: Fix the extract_list() utility function Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 05/17] utils: Back to use decode=True for the get_payload() Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 06/17] utils: Improve fix_utf8_char() Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 07/17] utils: Add catch_err() for the log message Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 08/17] logger: Initial work for the bot logger for future use Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 09/17] telegram: Use the created BotLogger() class Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 10/17] telegram: Add variable LOG_CHANNEL_ID declaration Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 11/17] telegram: Add send_log_file() in the DaemonClient() Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 12/17] telegram: Implement the log message for catching errors Muhammad Rizki
2022-12-24 21:22 ` Ammar Faizi
2022-12-24 21:39 ` Ammar Faizi
2022-12-21 1:33 ` [PATCH v4 13/17] discord: Add variable LOG_CHANNEL_ID declaration Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 14/17] discord: Use the BotLogger() to the GWClient() Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 15/17] discord: Add send_log_file in " Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 16/17] discord: Implement the catch erros and logs Muhammad Rizki
2022-12-21 1:33 ` [PATCH v4 17/17] Remove some unused imports Muhammad Rizki
2022-12-24 20:54 ` Ammar Faizi [this message]
2022-12-24 21:05 ` [PATCH v4 00/17] Fix, improvement and implement a bot logger Ammar Faizi
2022-12-24 21:09 ` Ammar Faizi
2022-12-24 23:31 ` Muhammad Rizki
2022-12-24 23:33 ` Ammar Faizi
2022-12-24 23:37 ` Muhammad Rizki
2022-12-24 23:34 ` Muhammad Rizki
2022-12-24 23:35 ` Ammar Faizi
2022-12-24 23:36 ` Ammar Faizi
2022-12-24 23:39 ` Muhammad Rizki
2022-12-25 11:16 ` Ammar Faizi
2022-12-25 11:29 ` Alviro Iskandar Setiawan
2022-12-25 11:34 ` Ammar Faizi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=167191522979.4153066.6052804702829285335.b4-ty@gnuweeb.org \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox