Score not syncing with FTC Events #682
Comments
|
If it matters, it was match 11 for event USIAJPM5.
If logs from the scoring system would be helpful we can collect them.
On Dec 18, 2023 10:33 AM, Jeramie Vens wrote:
<!--- DO NOT INCLUDE PRIVATE INFORMATION IN THIS ISSUE --->
**Describe the bug**
The last two weekends I have seen a match that did not sync to `ftc-events`. In both cases it was committed and posted just like the rest of the matches in FTC Live, and if I looked at the match history everything looked correct. To get it to show up on `ftc-events` I had to go to edit the score of the match, change something, change it back, save edits, and then commit the score again and then it synced.
The first time it happened was at `USIAMCM2` and that venue had very poor internet connection so I just blamed it on some internet hiccup at the time. I don't remember which match it was, but I believe it was towards the middle so probably somewhere around match 14-16.
This last weekend was at `USIAJPM5` and was I am pretty sure match 10. That school has excellent network connectivity, so I don't think it was anything on the internet link.
**To Reproduce**
Steps to reproduce the behavior:
1. Unable to reproduce
**Expected behavior**
All matches should sync to the ftc-events website.
**Screenshots**
N/A
**Device (please complete the following information):**
- Latest version available each weekend
- Different computers each weekend
**Additional context**
N/A
…--
Reply to this email directly or view it on GitHub:
#682
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
|
If you have access to the logs for either or both of those events, that would be helpful. We have seen the same symptom for several events the past 2 weeks, and believe we have narrowed down the cause of those. However, the two events you mention do not show up in our list of events impacted, so I suspect this is a different root issue. Note - if you see a match (or anything) not syncing, use the "Sync Now" button on the "Settings" tab to attempt a forced full sync instead of editing & re-committing a match. |
|
We've also had one match not sync in each of our first two Northern Nevada league meets: USNVNOM6, and USNVNOM1. (I have no idea how the events got numbered like that) We also fake-edited the match and committed, and the matches synced. We will use Sync Now in the future. I don't have the match numbers. I'll try to get the logs. |
|
2023_12_16_09_14_55_AM.log I don't see anything telling in the log file around the time of the match (Q-11) other than there is a However there are quite a few of those throughout the whole event. FYI, for this event we are running two fields with 6x tablets, 2x field displays, 2x audience displays, and two field displays tied into the streaming software. We also use two scoring server event streams to monitor match control events (one records the exact time of match triggers to make a video stream chapter list, the other is used by the streaming software to automatically switch between field cameras.) |
|
Log files attached. 2023_12_13_03_15_22_PM.log |
|
Log for |
Describe the bug
The last two weekends I have seen a match that did not sync to
ftc-events. In both cases it was committed and posted just like the rest of the matches in FTC Live, and if I looked at the match history everything looked correct. To get it to show up onftc-eventsI had to go to edit the score of the match, change something, change it back, save edits, and then commit the score again and then it synced.The first time it happened was at
USIAMCM2and that venue had very poor internet connection so I just blamed it on some internet hiccup at the time. I don't remember which match it was, but I believe it was towards the middle so probably somewhere around match 14-16.This last weekend was at
USIAJPM5and was I am pretty sure match 10. That school has excellent network connectivity, so I don't think it was anything on the internet link.To Reproduce
Steps to reproduce the behavior:
Expected behavior
All matches should sync to the ftc-events website.
Screenshots
N/A
Device (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: