The network might be a little boggy right now. TL;DR We're still mopping up from the bug that brought ~zod down last week.
-
Show this thread
-
The actual bug (which forced us to individually breach ~zod) was a related to the bytecode cache: we got rid of a clearing convention that...we shouldn't have gotten rid of.
1 reply 0 retweets 1 likeShow this thread -
So we breached ~zod, rebuilt the binary with this cache clearing logic and brought ~zod back up. Problem is: the rest of our ships were still using the old binary. What to do?
1 reply 0 retweets 0 likesShow this thread -
We ended up changing out the binaries and replaying the event log from scratch. This takes longer than it should, but it allows us to bring the ship state back to the original _and_ unborks the cache.
1 reply 0 retweets 0 likesShow this thread
Looks like all of the infrastructure stars have finished replay!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.