Database maintenance & upcoming code push

[mark]

Hi all!

I'm back, and announcing that I'm doing some database maintenance (very shortly) that should be mostly transparent, but will cause a minute or two of interruption (I believe). This is so I can update the security certificates on our databases and do a minor version upgrade. This operation was completed last week on the replicas, but now it's time to fail the leaders over and do the same operation to them.

Edit: Failover complete, blip has passed!

Secondly, we will be doing a code push! Possibly later tonight, but most likely, tomorrow sometime. We are putting together the usual Code Tour to describe what has changed. When I've got it, I'll share it before we proceed with the push.

Lastly, as far as I can tell, notifications have been pretty solid for the past 24 hours. If you are still actively not getting notifications you should, please comment and let me know?

Comments

[sunsetwanderer]

So far I'm getting notifs, but I've got a weird glitch when I'm replying to threads. I'll hit "post comment," but then it seems to refresh the page, and I have to press "post comment" again to have my reply go through. However, at least once when i did it, my comment went to the parent post in the thread, not the most recent comment.

Replying with this journal, since it's the only one I've used so far, so I don't know if it's happening with any of my other accounts.

[ranunculus]

I think I had a "had to hit post twice" thing happen to me last night.

[momijizukamori]

We were having an issue with cookies being cached, which caused forms to fail sometimes - it should be cleared up on the server, though you may need to clear your local browser cache as well - can you let me know if it's still happening after that?

[sunsetwanderer]

Looks like that might have taken care of it. Thank you!