Elite Dangerous | Server Maintenance 5 December 2024

Plus another 2-3 hours to create the cache, during which time there will be errors and everything will crash ...
I agree that outside of a short honeymoon period after a new feature is introduced and bug-fixed for a short period, General bug-fixes not related to recent new content always seem to be very much on the back burner.

And (and on a lighter note) I can pretty much guarantee that today's update will introduce many new bugs (into the Sol system).
 
Inara auto-updated the system’s state to invasion because the alert failed. Until someone gets in the game and provides the site with its proper status, after the Titan is in it, this information is of limited use…

Got all that info, very useful thank you. Looks like the first order of the day is to send scouts into Sol to see how bad it is.
 
Not necessarily.

Use your calculator and divide any natural number through 0. E.g. 5/0.
What is the result?
Is that a bug?

Type an ascii string into an address book field for a phone number.
What is the result?
Is that a bug?
Both of those are clearly bugs. If you divide by 0, you clearly didn't check your input data before doing the calculation. If you allow letters from ascii data in a search field for phone numbers (arguably ascii strings anyway), you are again not validating your input data and handling it in a nice way for the user. Programmers do these kind of checks all the time.

Without a look at the internal specifications for the service it's hard to say if it's actually a bug or just normal retry for something where the allowed time window is quite wide to start with.
The time a service should respond within is a contract and it is a bug if it doesn't respond in time. A retry is simply a workaround that smooths out some of those bugs. Whether it is an important enough bug to fix, is another story. Every user-facing system will have many more bugs "ignored" than those that are fixed. Retrying as a functionality is flawed and in my experience because you don't feel there is enough time to fix the root cause. It's basically saving developer time by letting the users spend more time waiting.
 
They've not announced a client patch, just extended server downtime, nor do the notes in this thread mention any fixes, so I wouldn't expect anything except whatever happens in Sol to be different.
I dunno why people keep hoping stuff will get fixed when the devs aren't even saying they're fixing anything. I know it's Christmas and all but people shouldn't be expecting presents from Santa. That said, I'm wondering why my launcher is saying Update. 🤪
 
All of the server hamsters are ready and waiting...

hamsters-sml.jpg
 
maybe true, but this can change quickly into the opposite if the player will experience all the bugs when they progress in the game and got deeper into gameplay. all poducts need a solid fundament and some quality, i would prefer buying a car which has proven its reliability and quality over one with the latest and greatest new (and buggy) features equipped.
and not to forget, frontier is destroying previously working stuff with some of their new releases, totally not to understand by me. i still be of the opinioin that frontier has a lousy (no) QA and if there were a seriusly altzernative on the market, the community here would probably fade away.
You did not quality check your spelling before publishing this comment. I'm just saying.. It's a bit ripe of you to call out bug hunting when you are not doing it yourself.
 
They've not announced a client patch, just extended server downtime, nor do the notes in this thread mention any fixes, so I wouldn't expect anything except whatever happens in Sol to be different.
We have had occasions in the recent past including but not limited to:
  • a candidate fix was accidentally missed from the announcement, and when we questioned it, FDev went "oh yeah we did fix that, forgot to say"
  • A deliberate fix went in with zero communication about it at all, and the bug is still open in the tracker, but... it's fixed.
  • Adding some related content fixed an issue with existing content
  • server behaviour changes in some way with zero announcement about it

On that last point, I am totally expecting this one to be true, and that's a good thing, and a change to the server side could affect the collector limpet bug and the FC transaction bugs, without code fixes, just bringing some things back into timeout windows, because they really do look like some sort of roundtrip behaviour oddity much like hyperjump.

I'm saying "bug" because the forum does, but of note, the Issue Tracker calls them "issues" and for some weird reason lots of people that purport to have deep development and QA knowledge here never use the word "defect" here. The distinction is important because otherwise you get into the language battles such as the one about hyperjump times. "Takes too long" really is better for users than "doesn't work at all" and yes that's an example of where mitigating a defect (by extending a timeout) will not necessarily take users from "there's a bug" to "bug fixed!"

So what I expect is... I expect the unexpected because 90% of the time that is what we get. And when it's the 10%, and there's nothing unexpected, it's unexpected to me, so I am still technically correct, which is the best kind of correct.

Next week with the Cobra V launch is when we're likely to get the client patch and any bug fixes that come with that.
This is a very good point but unpicking which issues will require client-side changes goes a bit deeper. (Since the servers started creaking it's become obvious that a lot of things that could happen entirely client-side actually don't, and we were getting away with that tech debt, and now we're not, because the servers are creaking.)
 
Back
Top Bottom