@OlegValteriswithUkraine I've patched MS to avoid the issue, so the "/post" page on MS is working again. However, I haven't found the
actual cause for the value of the post's cached
post_comments_count
, which should be a minimum of 0, being -1. What appears to have happened is that, for some reason, when Redis generated its cache of
this report something ended up messed up sufficient for the cached count of comments to be -1, which, obviously, isn't legit. I was also able to cause Redis to re-generate its cache for that post, which has resolved the remaining display issue on "/posts". I am, however, a bit surprised that the cached copy wasn't automatically expired from Redis, as I thought that should happen after an hour.