Bug Report - Reading Bibs Assigned to an Unstarted Event as Unassigned Bibs

[James Er Ralston]

We timed a race this weekend that included a 10K race followed by a 5K race.  During the 10K race, 5K bibs were being picked up as unassigned bibs.  We had both races open and only the 10K race started.  This was happening on both our primary and backup systems. We are running the latest version 1.6.6.3 and using dynamic bib assignment.

You can see an example in the attached screenshot for bib 1533.  The 5K race had 4 digit bib numbers and the 10K race had 3 digit bib numbers.   This screenshot was early in the race and many more occurred after that.  To make matters worse, we deleted these reads before starting the 5K race, but some of these got converted to chip start times which we then had to correct as well.  

Brian, I sent you the race database by private email, so hopefully you can figure out why this happened. 

[Brian Agee]

You're correct! I just tested this and got the same results. I rewrote the method that handles tag reads to make it more efficient, but one line of code was only looking at "started" races to see if the chip read was valid, but it should have been looking at all races. I have it fixed and will push out an update tomorrow. Thanks!