I am running 169 from a few hours ago, although this happened with 167, at least, as well. While catching is running, I can go to My Pokémon and right-click to Powerup something. The powerup will succeed and be logged in between a couple of the other catching-related actions, fine, but if I switch back over to the Pokefarmer tab to see if I have enough stardust to continue powering up, the Stardust has not been decremented at all and has probably increased by 100 for each pokemon that has been caught since I last looked, even though the Powerup should have used several 1000 stardust, so I can easily exhaust the stardust without the displayed number showing any evidence of the situation, and I have to rely on an error being returned from Niantic's servers about resources being exhausted, instead of just being able to quit when the number is low. The real, much lower Stardust number does show once the session expires and a reclogging occurs, which presumably re-reads all the stats from the server. There are other issues, like the CTP seems to always be too low, at least by 1 and maybe more than 1, so if the candies says 8 and the CTP says 4, when I power up, I expect there to be 4 candies left, but there are only 3, so obviously 5 candies were used instead of the indicated CTP number of 4. Again, this can easily lead to a not-enough-resources-error and potential flag by Niantic for botting. Finally, more related to the Stardust being wrong, once a session-expired-relogging occurs, the stardust number is updated, but then the stardust/hour number goes negative. The release notes indicate something about this was fixed, but maybe not quite enough, since things are still haywire after the occasional expire-relog. Ok, the aforementioned behavior is not visible in the logs, meaning you have to actually run the bot and do powerups to see it, but here is a recent 169 log that includes a few powerups.
