updated scoreboard of dallas regional

[plnyyanks]

Originally Posted by Mike Soukup

It's sad that this has been a common theme for so many years. I guess this is what happens when you only get your server online a few days before events start. That's not enough time to load test it or fix the inevitable bugs.

What's even more frustrating is the fact that there has been almost zero communication all day about the problems, or an estimated fix timeframe. All we've heard is a post of TeamForge saying they're working on it at 10 AM. I get they're busy with competitions and all, but a "hey, our database melted, but it should be back up tomorrow" isn't that time consuming.

Hopefully they get everything ironed out quickly; I think I'd prefer the old HTML pages to a buggy API.

[Mike Soukup]

Originally Posted by plnyyanks

What's even more frustrating is the fact that there has been almost zero communication all day about the problems, or an estimated fix timeframe. All we've heard is a post of TeamForge saying they're working on it at 10 AM. I get they're busy with competitions and all, but a "hey, our database melted, but it should be back up tomorrow" isn't that time consuming.

Hopefully they get everything ironed out quickly; I think I'd prefer the old HTML pages to a buggy API.

My fear is that no news is bad news. If they knew how to fix the problem and how long it would take, they'd probably let us know on TeamForge.

Maybe they can just push the results to Spyder or TBA directly, we both know how to handle the load

[plnyyanks]

Originally Posted by Mike Soukup

My fear is that no news is bad news. If they knew how to fix the problem and how long it would take, they'd probably let us know on TeamForge.

Maybe they can just push the results to Spyder or TBA directly, we both know how to handle the load

That's probably the unfortunate truth. My guess is that caching was lacking and couldn't handle all the load - some of the endpoints get really specific with lots of parameters. I can see that being difficult to cache properly, especially when the data is updating rapidly.

We should also get Chezy Arena to replace FMS and get a nice, full stack, open source solution.

TBA also has an authenticated push API built, which allows a field system to post results in realtime, just sayin' (nudge, nudge )

[SoftwareBug2.0]

Originally Posted by Mike Soukup

My fear is that no news is bad news. If they knew how to fix the problem and how long it would take, they'd probably let us know on TeamForge.

Maybe they can just push the results to Spyder or TBA directly, we both know how to handle the load

Yeah, I mean if things were even "sort of ok" rather than "equipment caught fire" they could release a CSV or something like the output of "mysqldump".

[MrRoboSteve]

I know it's frustrating, but I also know firsthand they've been very busy fixing issues that were blocking match running. We're just going to need to be patient-be assured that they know there's an issue and will work on it at the appropriate priority.

[plnyyanks]

Updates from FIRST this morning:

Hi Dave,

I understand your frustration. We are working to resolve the issues with the API, but also must focus on supporting the
events at the same time.

The issue we are working through involves the data sync between the local computers at the events and our Azure database
which is the data source for the event web pages and the API.

Regards,
-Matt

...So I would guess we're not getting data this weekend

[Eugene Fang]

Hi Dave,

I understand your frustration. We are working to resolve the issues with the API, but also must focus on supporting the
events at the same time.

The issue we are working through involves the data sync between the local computers at the events and our Azure database
which is the data source for the event web pages and the API.

Regards,
-Matt

I don't get how a data sync issue between events and Azure causes the timeouts/500 errors we're seeing. If there is an issue with data sync, wouldn't the data served by the API just be stale?

[Mike Soukup]

Originally Posted by Eugene Fang

I don't get how a data sync issue between events and Azure causes the timeouts/500 errors we're seeing. If there is an issue with data sync, wouldn't the data served by the API just be stale?

It would explain why some events have updated rankings, but not matches. It wouldn't explain the massive timeouts & 500 errors. They should be serving empty data. Unless they shut it down today because there were sync problems that only showed up when the DB was under a massive reading load. All speculation.

Until then I'll just reply to all the 1 star ratings for Spyder with a boilerplate "FIRST screwed this up, not us" message.

[Eugene Fang]

Originally Posted by Mike Soukup

Until then I'll just reply to all the 1 star ratings for Spyder with a boilerplate "FIRST screwed this up, not us" message.

Yeah, the ratings are rough

[Ether]

Originally Posted by plnyyanks

I hope the data is being safely archived in the local computers, and not lost forever (like the Twitter data in previous years).