singulart/joy-disco-bots

Joystream Discord Bots

Hello, world! I'm Lex (not to be confused with Lex Fridman!), and this Github shows some of my open source projects in AWS, Java, Python and Typescript.

How to get in touch with me

Tox messenger

TOX ID: A9BABF05A0CE34F6B0812C999BA3F0487DD16F620AA2019A74E525EE026237362427C1A9ED2E

Signal app

Signal me

ICQ

Like in good old days..

joy-disco-bots's Issues

User re-entering Discord can't restore their server roles

1. User successfully verified with the bot using /claim + /solve flow
2. User leaves the Discord
3. User re-enters the Discord
4. User observes their custom roles are gone and tries to verify again
5. Error message is shown: this identity is already claimed

Expected result should be that user is able to run the verification again and restore their custom server roles.

Bot crashes when /claim command sends non-existent member handle

/claim <bogus member ID> <some wallet> causes the bot to crash because the queryNodeClient.memberByHandle throws an Error after some number of retries.

Fix: add graceful error handling

Additional check for storage provider nodes

1. Given a storage node doesn't respond to ping probe.
2. When Retrieve the list of bags for this node by its ID
3. Then Check whether all bags have only 1 bucket
4. Then Send notification to Discord only when 3 is false.

Requested by @0x2bc

Bot sends too many notifications to #general channel

Is was suggested to reduce the volume of forum notifications in #general channel.

Healthy SP node is being reported as faulty

The bot reports the SP node https://joystream-storage.bwarelabs.com/storage/ as unhealthy despite it successfully recovered from short-term downtime.

Salary payouts that repay WG debt show up as FAILED

When a working group owes certain amount to its workers, the working group debt occurs. During the next payout, system makes an attempt to remove that debt by paying workers extra. The working groups bot has a small error in its business logic, which renders such transactions as FAILED on Discord.

Improve role sync loop performance

As the number of verified users have grown and reached ~150, it became evident that querying memberships from Query Node one by one is not future-proof solution.

It would be good to add bulk querying backed up by cache of sorts, so that role sync loop doesn't bombard QN with queries.