
Though I don’t quite yet, as I promised to leave a decent writeup for the other dev (who’s off this week) of the stuff I’ve discovered about the obscure data issue we’ve been battling, and the various tools I’ve created to help track it down. This would have been done, but stuff that worked locally wasn’t working when deployed, and has been driving me up the wall for half the afternoon - until I realised I’d forgotten to push the most important changes to said tools

Anyway, that should all work now, and I’ll have full details of the specific 25 rows of data (out of around 21,000) that are causing the problem. The people we do this for can then have a look at them and work out what they want to do about it; it’s very likely to be a simple case of random user errors that have accumulated over the past year. With that done, it’ll only take about twenty minutes to write it up, so I’ll probably get around to it while dinner’s in the oven or maybe tomorrow - it just has to be ready for the other dev on Monday morning



).



. <click>
Leave a comment: