CCP_Explorer

We’re still on day #1, the main part of the experiment starts after 11 o’clock EVE Time tomorrow.

That system needs to be reworked to not depend on a DB job during downtime, before we make fewer downtimes the norm.

For the regular asteroid belts: Confirmed.

There should be. If there are any daily things that you do or claim today, and then you can’t tomorrow; then please create a bug report and ping me here again with the EBR number.

Since you ask; it has happened, on test servers, that devs have put suns into their cargo holds. It was fun.

It has also happened, on TQ, through misbehaving code that has now been fixed, that the Universe Root was put into a structure that was in a ‘Inventory Graveyard’ (inventory items that are deleted are first moved from the main inventory table into graveyards and then later archived). It was not fun, it caused endless loops in the inventory system under certain conditions since the root item now had a parent.

Yes, there was downtime today, Wednesday, and will be downtime again on Friday.

Currently they are actual real items in the inventory system that are replenished during downtime in a DB job while the inventory system is offline. Since the cluster doesn’t go offline then the inventory system is still up-and-running and then the DB jobs must not run.

There are longer-term ideas on how to replace the asteroid belts. Currently they are actual real items in the inventory system that are replenished during downtime (in a DB job while the inventory system is offline) and need to be replaced with sites that spawn based on a distribution and regularly replenished.

That is possible, but more complicated than simply reducing the number of downtimes (and eventually getting rid of them).

Not by any meaningful amount. We were at 4 minutes today and we can realistically only hope to shave off seconds here and there. Any effort towards signifi...

That should not be legal!

The issue isn’t that we’re lacking a time sync source, a regular NTP will do just fine. It was getting old code to do new things, such as listening to that NTP source and correcting itself regularly while always moving time forward.

This is not related to the #nodowntime experiment. The login server (SSO) was updated at 10:30 on Monday morning.

Neither; but more the former. It wasn’t targeted optimization but rather code and hardware changes that then resulted in less memory pressure.

Sometimes the changes are internal. For example, in the last 10 days or so, the majority of the updates were build system or technology framework fixes.

The regular asteroid belts do not get replenished.

The engineers had a bit of a breakthrough late this afternoon; it looks like an object/memory leak in the camera that ultimately manifests as audio issues.

What is the bug report number (EBR-xxxx)?

Cloudflare has resolved Cloudflare Status - Magic Transit Routing issues.

Please see ongoing incident Cloudflare Status - Magic Transit Routing issues at Cloudflare.

Hello all – I’m going to try and cover some of the things you mention here in this thread.

Sorry, very long post; I recommend you get your favorite beverage.

But first a recent network/disconnect experience I had with a realtime online bike simulator I use for my training: Zwift (https://www.zwift.com/) that I’ll use for comparison and reference. Zwift is a single-shard multi-world setup, just like EVE is a single-shard multi-solarsystem setup. When I was riding in the afternoon on 26 Jan (doing a warmup) I noticed that the rider list disappeared and then the event I was going to didn’t show up...