Open runbeyond opened 4 years ago
I was unable to reproduce this bug. I couldn't get a registration in the database without a birth date and/or gender with mobile or desktop.
@ColinW520 @runbeyond I did some research and based on my data dump (my Participant.last is 7-16-2020) I found the below participants had issues with their registrations. Most of them had nil values for everything after division, including "accepts waiver". There was one that had an empty string for division and nil for birth_date. There was another one that had an address and most other fields ok but an empty string for division and nil for birth_date. You can see below they were all clustered in a 3 week period about a year ago.
Participant Id | Registration Id | Date |
---|---|---|
875 | 824 | 9-18-2019 |
877 | 821 | 9-19-2019 |
859 | 809 | 9-13-2019 |
889 | 836 | 9-23-2019 |
878 | 826 | 9-19-2019 |
837 | 790 | 9-5-2-19 |
880 | 828 | 9-22-2019 |
1037 | 754 | 10-5-2019 |
1039 | 976 | 10-6-2019 |
841 | 784 | 9-5-2019 |
There were a couple of commits involving registrations just after the last one. I'm checking to see if one of those may have resolved the issue. @runbeyond Is there a recent instance of this happening?
I can’t be sure when I saw the last instance of this. Perhaps some participants for Sky Island 2020 but it’s not really something we look for.
It had been a prominent problem early on and I would see it a lot when managing race timing. It’s been since March 1 2020 that I didn’t any race timing work.
Now, we only notice it if we see it while editing a participant record. And I can’t be sure whether what we saw was isolated to the bug Colin recently resolved or related to a separate bug that allows users to submit a request w/out those fields populated or a bug that somehow lost that data (for lack of a better explanation).
We will start timing racing again with Wonderland so I will see any new instances of this issue if they arise.
On Tue, Oct 13, 2020 at 3:15 PM William Blake notifications@github.com wrote:
There were a couple of commits involving registrations just after the last one. I'm looking into those to see if one of those looks like it may have resolved the issue. @runbeyond https://github.com/runbeyond Is there a recent instance of this happening?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spectrumtrail/spectrum/issues/173#issuecomment-707982682, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKUR7DIMR5PBCKAK5ODB3D3SKSYOLANCNFSM4SEYP2YA .
Actually, scratch that. The Rails console limits results to the most recent 11 records by default. When I open the scope to all records there's actually 140 of them. They're also right up until my data dump so I think it's a more pressing issue than I realized.
Some registered participants are missing age and gender data. We do not currently have a way to replicate this bug.