Fwd: Team Nick Name

26 views
Skip to first unread message

Greg Marra

unread,
Feb 10, 2016, 2:52:36 PM2/10/16
to theblueallian...@googlegroups.com
Are we aware on any problems with our TIMS scraping currently?

We should probably make the cron scrapes update a sitevar with the last time they successfully completed. This would let us build a little dashboard about their health.

---------- Forwarded message ---------
From: <svhs...@gmail.com>
Date: Wed, Feb 10, 2016 at 6:51 AM
Subject: Team Nick Name
To: con...@thebluealliance.com <con...@thebluealliance.com>


 

Hello,

I’m a team representative of Team 5429 in Las Vegas, Nevada. We have been noticing for over a month now that our team nick name has not changed. The Blue Alliance lists us as “ Serious Voltage” but we changed our nick name in our TIMS account and now lists us as “ Black Knights” if you can make this change it would greatly be appreciated.  

 

-Javier R

Team 5429

 

Phil Lopreiato

unread,
Feb 10, 2016, 3:07:05 PM2/10/16
to theblueallian...@googlegroups.com
Interesting, the API show the correct name currently.

@Greg or Eugene - can you look at the Team in the ndb and see what the last modified timestamp is?

Maybe it's the page cache not being cleared?



Phil Lopreiato
--
You received this message because you are subscribed to the Google Groups "thebluealliance-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to thebluealliance-dev...@googlegroups.com.
To post to this group, send email to theblueallian...@googlegroups.com.
Visit this group at https://groups.google.com/group/thebluealliance-developers.
For more options, visit https://groups.google.com/d/optout.

Greg Marra

unread,
Feb 10, 2016, 10:11:27 PM2/10/16
to theblueallian...@googlegroups.com
Are you sure? I'm seeing "Serious Voltage" on the API, which is the wrong nickname.

pasted1
I'll peek at the ndb later.

Phil Lopreiato

unread,
Feb 11, 2016, 9:58:09 AM2/11/16
to theblueallian...@googlegroups.com
Oh, sorry, I mean the FRC API was showing the correct value, which means its something on our end most likely.

Phil



Phil Lopreiato
Reply all
Reply to author
Forward
0 new messages