Update stats endpoint and CLI to use Supabase broadcast about capgo HOT 16 CLOSED

Instead of creating a new table, we use SELECT * FROM pg_stat_activity WHERE channel = 'my_channel' to get all the subscribers that are connected to a particular channel, if the the rows > 0 then will broadcas the messages.

cc: @riderx

from capgo.

💎 $50 bounty created by Capgo
🙋 If you start working on this, comment /attempt #411 to notify everyone
👉 To claim this bounty, submit a pull request that includes the text /claim #411 somewhere in its body
📝 Before proceeding, please make sure you can receive payouts in your country
💵 Payment arrives in your account 2-5 days after the bounty is rewarded
💯 You keep 100% of the bounty award
ℹ️ If something is not clear ask before working on it, otherwise your chance to rework it is high
🎥 To claim you need to provide in your PR a demo video of the change
👨‍👩‍👧‍👦 Join the Discord to get help
📏 Check all Bounty rules
🙏 Thank you for contributing to Cap-go/capgo!

from capgo.

/attempt #411

from capgo.

Proposal:
Hey @riderx, instead of subscribing to normal channel, I'm gonna directly subscribe to database changes: https://supabase.com/docs/guides/realtime/subscribing-to-database-changes
And instead of doing while(true) will take the changes returned from subscribed channel and call uploadData func

from capgo.

@5war00p this is not possible, because the CLI do not login like user but with API key.
So RLS cannot work.
And in top of that in production now we use ClickHouse so the data are not stored to supabase anymore so the solution shouldn't watch stats table, but something else.

from capgo.

I'm sorry I didn't gave the background on why this is already like this ^^

from capgo.

Hm, then realtime broadcast is the one we should be looking into. In that case we need to open a channel connection on sending side and broadcast, so you are saying create a new table to track each client logs state. right?

from capgo.

@5war00p: Reminder that in 5 days the bounty will become up for grabs, so please submit a pull request before then 🙏

from capgo.

The bounty is up for grabs! Everyone is welcome to /attempt #411 🙌

from capgo.

/attempt #411

from capgo.

@mrkirthi-24: Reminder that in 5 days the bounty will become up for grabs, so please submit a pull request before then 🙏

from capgo.

The bounty is up for grabs! Everyone is welcome to /attempt #411 🙌

from capgo.

I will be attempting this. I figured out how to authenticate as a user using JWT from CLI. (How to authenticate using apikey while generating JWT) thus the 'So RLS cannot work' is no longer relevant

/attempt #411

from capgo.

@WcaleNieWolny: Reminder that in 5 days the bounty will become up for grabs, so please submit a pull request before then 🙏

from capgo.

The bounty is up for grabs! Everyone is welcome to /attempt #411 🙌

from capgo.

This has been fixed by using Clickhouse direct read for now with a loop

from capgo.