Create a "display" interface to show results to racers as they pass the finish line.

Use QML for display and enter into the contest

As racers cross the finish line, display results such as: Name, Time, Avg. MPH, Prizes won, etc.

@golfsmed83

Importing CSV files is great, but there's still a lot of walk-up racers. Fat fingering the input can ruin your race results. E.g., a female getting 2nd place in the 30 year old man bracket! (Not that this actually happened.)

Making this for walk-up racers puts the onus on the registrant to input the correct data.

Moving to racergo an audit log was created which tracks all linkBib actions so that if/when things go wrong with data entry, you can track down where/how and fix the results.

We need to add an interface to see the audit log and modify results manually.

The race doesn't score the race properly in these cases

Qr snapper is a good start

https://qrsnapper.appspot.com/

when adding runners, an error in submitting the form wipes/clears the form -- don't do that

When entering bib results, require confirmation as a second entry.

Could make a Confirmed bool in the Result/Entry struct that is set when confirmed by a second data input of the same bib # in linkBib. If an Entry/Result isn't confirmed, display it as bright red in the user interface and allow for manual action to fix the issue.

Bandits are those individuals that run across the line (and we record a time for them) except they don't actually have a bib or are part of the race

SIGSEGV: segmentation violation
PC=0x7f715ecd5224
signal arrived during cgo execution

main._C2func_cwiid_command(0x0, 0x200000003, 0x0, 0x0, 0x0, ...)
github.com/mzimmerman/racerwiigo/_obj/_cgo_defun.c:45 +0x2f
main.raceFunc()
github.com/mzimmerman/racerwiigo/_obj/_cgo_gotypes.go:243 +0x470
created by main.main
github.com/mzimmerman/racerwiigo/_obj/_cgo_gotypes.go:186 +0x159

goroutine 1 [IO wait]:
net.runtime_pollWait(0x7f715f2dff00, 0x72, 0x0)
/usr/lib/go/src/pkg/runtime/znetpoll_linux_amd64.c:118 +0x82
net.(_pollDesc).WaitRead(0xc200131110, 0xb, 0xc200123150)
/usr/lib/go/src/pkg/net/fd_poll_runtime.go:75 +0x31
net.(_netFD).accept(0xc200131090, 0x7109a0, 0x0, 0xc200123150, 0xb, ...)
/usr/lib/go/src/pkg/net/fd_unix.go:385 +0x2c1
net.(_TCPListener).AcceptTCP(0xc200000368, 0x18, 0xc2000ca010, 0x4660b7)
/usr/lib/go/src/pkg/net/tcpsock_posix.go:229 +0x45
net.(_TCPListener).Accept(0xc200000368, 0x0, 0x0, 0x0, 0xc2001230f0, ...)
/usr/lib/go/src/pkg/net/tcpsock_posix.go:239 +0x25
net/http.(_Server).Serve(0xc200103140, 0xc2000fd8c0, 0xc200000368, 0x0, 0x0, ...)
/usr/lib/go/src/pkg/net/http/server.go:1542 +0x85
net/http.(_Server).ListenAndServe(0xc200103140, 0xc200103140, 0x0)
/usr/lib/go/src/pkg/net/http/server.go:1532 +0x9e
net/http.ListenAndServe(0x6927c0, 0x5, 0x0, 0x0, 0x1, ...)
/usr/lib/go/src/pkg/net/http/server.go:1597 +0x65
main.main()
github.com/mzimmerman/racerwiigo/_obj/_cgo_gotypes.go:191 +0x287

goroutine 2 [syscall]:

When racers were unconfirmed and many other racers come in before the non-confirmation is addressed, the interface cuts off the view to only but the last 10, so there's no way to still know which bibs are unconfirmed.

Show unconfirmed racers at the top.

Set up this interface to be a authoritative of when the racer finishes. this would be someone who would be scanning bibs or entering the numbers based off of a slower process and is not necessarily entering the bib number at the time of the crossing of the finish line

Add a near real-time interface so that clients don't have to refresh to get new data; it gets pushed to them.

This is primarily to be able to announce runners as they come across the line.

During a race, hardware failure could cause a loss of all race results. Implement some "mirroring" with another local laptop/server. This could include an active-active partnership or active-passive, but it should support rolling over fairly automagically.

If racergo were to accept electronic times from the time machine, and also enter/accept bib #'s by time, make racergo "smart" to pick the best bibs to line-up against the most accurate times. This one is yours @golfsmed83

https://www.twilio.com/blog/2014/06/sending-sms-from-your-go-app.html