Participants tab isn't showing the correct numbers.

[frankchen07]

Describe the bug

The participants tab on a hackathon's page is not displaying the correct number of participants

To Reproduce

1. go to any hackathon prize explorer view and look at the participants tab with the number after it

2. compare to metabase registrant numbers

Expected behavior

registrants and participants counts should match

[walidmujahid]

Where is the metabase number coming from? Or perhaps: what do mean by 'metabase'?

Currently, the hacker_count for the page is the counting all HackathonRegistration instances. After tests in my local docker build, I believe I have identified a design oversight in the hackathon_registration endpoint connected to the onboarding page. When "Join Now" is pressed on the onboarding, a user can continue pressing the button from the frontend and the hackathon_registration endpoint will continue creating duplicate HackathonRegistration instances.

Now, the most straightforward solution to this probelm that I can think of is to just use whatever queryset or method that the metabase number uses.

However, correcting the hackathon_registration endpoint design flaw by adding some validation would also solve this problem and should be done anyway in my opinion -as a separate issue although it may be connected to this current issue. Furthermore, changing the query for hacker_count for the hackathon page so that it ensures dinstinct users per hackathon event could be of benefit.

[frankchen07]

the metabase number is just counting distinct profile_ids that have completed the registration.

It could be that the participants number is just creating duplicate hackathon_registration instances, and that is being counted more than once. It seems to make sense because the participants number is higher than the metabase number.

in our case metabase = psql database that I'm working off of.

[walidmujahid]

the metabase number is just counting distinct profile_ids that have completed the registration.

It could be that the participants number is just creating duplicate hackathon_registration instances, and that is being counted more than once. It seems to make sense because the participants number is higher than the metabase number.

in our case metabase = psql database that I'm working off of.

Okay. I believe thet counting distinct registrants should solve this problem. Tested locally. PR opened: #7071

I opened another issue for the duplicate HackathonRegisteration instances: #7070