http://blog.code.org/post/156133016748/this-mornings-technical-difficulties-on-code

The way we store student coding activity is in a table that until today had a 32-bit index. What this means is that the database table could only store 4 billion rows of coding activity information. We didn’t realize we were running up to the limit, and the table got full. We have now made a new student activity table that is storing progress by students. With the new table, we are switching to a 64-bit index which will hold up to 18 quintillion rows of information. On the plus side, this new table will be able to store student coding information for millions of years. On the down side, until we’ve moved everything over to the new table, some students’ code from before today may temporarily not appear, so please be patient with us as we fix it.

We sincerely apologize for the disruption to your classroom and any inconvenience this may have caused. Thank you for using Code Studio. Our engineers are working hard to resolve this issue as quickly as possible.

Trust the "cloud".

 

On the plus side, this new table will be able to store student coding information for millions of years.

Or at least until 03:14:07 UTC on Tuesday, 19 January 2038.

 

To err is human.
It takes a computer to really f#%* things up.

 

Or at least until 03:14:07 UTC on Tuesday, 19 January 2038.

Interesting... mind clarifying? Is that date related to the limitations of a 32-bit system?

 

Interesting... mind clarifying? Is that date related to the limitations of a 32-bit system?

Y2K38 Problem.

 

Y2K38 Problem.

I learned something new today! ... thanks!