* Update sebi_machine_launcher.sh
* Update sebi_machine_launcher.sh
* Update requirements.txt
* removed numpy import
* Fixed a stupid typo.
* Fixed broken import someone didn't check.
* Updated bot_management.py
* Updated bot_management.py
* Update bot_management.py
* Update bot_management.py
* Update bot_management.py
* Added ban command
And changed the response because if you were talking without commas you would need to breathe heavily and and and and *huff*
* Update bot_management.py
* Aaa
wrong word lmao
* Update bot_management.py
Requirements file was missing five requirements. This might be useful to
have fixed, so I sorted that out.
- opuslib
- youtube_dl
- asyncpg
- PyNaCl
- dataclasses
Made the sebi_machine_launcher.sh executable only under the current
owner.
Added a SIGINT trap to sebi_machine_launcher.sh. You are only restarting
while the bot returns a non-truthy exit code (i.e. non zero). SIGINT,
which triggers the Python KeyboardInterrupt builtin exception being
raised will, if unhandled, result in a non-zero exit code. Thus, if you
provide a keyboard interrupt, you will just have the bot instantly
respawn. This is fine until you have a one second lag over SSH. Then my
wrist starts to hurt from spamming CTRL-C so many times until the bot
process dies.
