gdgpisa / gdgpisausermanager Goto Github PK

Thanks for reporting this issue with our bot 😁❤️
Please fill-in the details and remove the useless sections

When you add a user:

2018-09-24 10:59:47,216 - ERROR - An uncaught error was raised while processing the update
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/telegram/ext/dispatcher.py", line 279, in process_update
    handler.handle_update(update, self)
  File "/usr/local/lib/python2.7/dist-packages/telegram/ext/messagehandler.py", line 169, in handle_update
    return self.callback(dispatcher.bot, update, **optional_args)
  File "gdgpisausermanager.py", line 44, in welcome
    threading.Timer(Config.WAITING_TIMEOUT, timer,
AttributeError: type object 'Config' has no attribute 'WAITING_TIMEOUT'

We should create a "test group" and try what happens if multiple users join at the same moment or with a few seconds of delay

This is the log:
set 18 13:50:26 raspberrypi python[12935]: bot.kickChatMember(chatid, userid, until_date=25) set 18 13:50:26 raspberrypi python[12935]: File "/usr/local/lib/python2.7/dist-packages/telegram/bot.py", line 60, in decorator set 18 13:50:26 raspberrypi python[12935]: result = func(self, *args, **kwargs) set 18 13:50:26 raspberrypi python[12935]: File "/usr/local/lib/python2.7/dist-packages/telegram/bot.py", line 1428, in kick_chat_member set 18 13:50:26 raspberrypi python[12935]: result = self._request.post(url, data, timeout=timeout) set 18 13:50:26 raspberrypi python[12935]: File "/usr/local/lib/python2.7/dist-packages/telegram/utils/request.py", line 278, in post set 18 13:50:26 raspberrypi python[12935]: **urlopen_kwargs) set 18 13:50:26 raspberrypi python[12935]: File "/usr/local/lib/python2.7/dist-packages/telegram/utils/request.py", line 215, in _request_wrapper set 18 13:50:26 raspberrypi python[12935]: raise BadRequest(message) set 18 13:50:26 raspberrypi python[12935]: BadRequest: Peer_id_invalid``

Expected Behavior

If the users the first time doesen't complete the registration, when someone add the member again and he/she complete the registration everything should be fine

Actual Behavior

when the user complete the registration the second time, he/she get banned

Steps to Reproduce the Problem

1. add the member to the group and don't complete the registration
2. when the user get kicked, add it again to the group
3. this time complete the user registration
4. after the timer the user get kicked out

Specifications

• Python: 3.7
• Operating System: raspbian

I suppose that depends on the last commit

Expected Behavior

Running the bot it should load config.py, that search for the .telegram.token file. If the file does not exist it should suggest where to put it.

Actual Behavior

ModuleNotFoundError: No module named 'config'. Installing as a module it copy only the gdgpisausermanager.py file, so config.py is unreachable.

Steps to Reproduce the Problem

Just follow the README.md instruction to install the bot.

Specifications

• Python: v 3.7
• Operating System: Windows 10 build 1803, Ubuntu server 18.04.1 LTS

When a user clicks the InlineKeyboardButton, the bot will automatically accept new users. We need to check if the user who clicks the button is the same users who joined

To be discussed.
A CI that builds the docker image and publishes it on the Docker Hub can be useful.

Since the project is open source, can be implemented for free using Travis-CI, that is a simple but powerful tool that anyone should understand.

There are some tools that simulate the Telegram server and sends programmatically fake requests to our bot.

Should be tested:

• all the code, possibly with ~100% coverage
• usernames and nicknames with strange characters (UTF-16, emoji, etc.)
• stress test: two users come consequently, the bot should show 2 different buttons, one for each user, and other things like that.

Related: Stress Test #3

Simply there are no translation. I think is not so urgent but it could be useful for other groups.

Thanks for reporting this issue with our bot 😁❤️
Please fill-in the details and remove the useless sections

Expected Behavior

We should create an appropriate output log

Actual Behavior

The bot prints everything inside the Terminal window

Steps to Reproduce the Problem

1. Run the bot

Screenshot

If possible provide a screenshot of the problem.

Specifications

• Python: Python & version
• Operating System: Windows, Mac, Linux

As the title says, we should update the README file with better infos

Warning in gdgpisausermanager.py. See https://git.io/fxJuV for details.

Adding use_context=True as suggested seems broking the bot (at least on Docker).