Got a ton of machinelearning api errors after I createe a new memetracker and hit refresh for the first time.

See for yourself.

http://pastebin.com/m32869a2d

Comments

kyle_mathews’s picture

kyle_mathews commented

Yeah, that's more shocking looking than bad. Distance scores between nodes are stored in the database. If a distance score is already stored in the database, it shouldn't be recalculated again. Sometimes (herein lies the bug) they are and when Memetracker tries to insert them again into the database, the database complains.

So this bug, while annoying, doesn't actually harm anything other than wasting a bit of processor time recalculating distance scores.

Thanks for the bug report -- I'll see if I can out why distance scores are being recalculated.