Open Bug 2000000 Opened 1 month ago Updated 1 month ago

2 000 000 Bugs! Celebrate!

Categories

(bugzilla.mozilla.org :: General, enhancement)

Product:
bugzilla.mozilla.org
Component:
General
Version:
Production
Type:
enhancement

Tracking

()

People

(Reporter: maxx, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

Attachments

(2 files)

twomillion.jpg
53.15 KB, image/jpeg
Details
fancier estimate of our bug filing velocity
166.45 KB, image/png
Details

2,000,000 Bugs!

🎉🎉🎉🎉🎉

There is no greater feeling than a code base with 2,000,000 bugs in it.

LOL, missed it by 2 woohoo!!

/me bows

Congratulations, Bugzilla! You did it!

Wow, it's incredible to reach this milestone.

Here's to two million more! 🎉

TWO MILLION

🚀🎊🎆

🥳🎉🎊🎉🎉🥳🥳🥳🎉🎉🎊🎊🎊🎉🎉🥳🥳🎉🎉🎊🥳🎉🎊🎉🎉🥳🥳🥳🎉🎉🎊🎊🎊🎉🎉🥳🥳🎉🎉🎊🥳🎉🎊🎉🎉🥳🥳🥳🎉🎉🎊🎊🎊🎉🎉🥳🥳🎉🎉🎊🥳🎉🎊🎉🎉🥳🥳🥳🎉🎉🎊🎊🎊🎉🎉🥳🥳🎉🎉🎊🥳🎉🎊🎉🎉🥳🥳🥳🎉🎉🎊🎊🎊🎉🎉🥳🥳🎉🎉🎊🥳🎉🎊🎉🎉🥳🥳🥳🎉🎉🎊🎊🎊🎉🎉🥳🥳🎉🎉🎊🥳🎉🎊🎉🎉🥳🥳🥳🎉🎉🎊🎊🎊🎉🎉🥳🥳🎉🎉🎊🥳🎉🎊🎉🎉🥳🥳🥳🎉🎉🎊🎊🎊🎉🎉🥳🥳🎉🎉🎊🥳🎉🎊🎉🎉🥳🥳🥳🎉🎉🎊🎊🎊🎉🎉🥳🥳🎉🎉🎊🥳🎉🎊🎉🎉🥳🥳🥳🎉🎉🎊🎊🎊🎉🎉🥳🥳🎉🎉🎊

🪲🦗🐛🪲🐛🪲🪲🪲🪲🦗🪲🪲🦖🪲🦗🐛🪲🐛🪲🪲🪲🪲🦗🪲🪲🦖🪲🦗🐛🪲🐛🪲🪲🪲🪲🦗🪲🪲🦖🪲🦗🐛🪲🐛🪲🪲🪲🪲🦗🪲🪲🦖

Roar! 🦖

I can reproduce this on my machine. Congrats! 🦖

The Book of Mozilla, 13:11

And lo, the Tinkerers looked upon the ledger and saw two million entries of their own creation.

The Elders trembled, for the Bugs were countless and unending,
yet from their chaos sprang clarity.

Out of the swirl of regressions and patches arose a new flame,
forged not of perfection, but of persistence.

“Let there be one more,” spoke the Maintainer,
“for as long as we file, we fight.”

And the world was once again made open.

Attached image twomillion.jpg —

🥳🎉 incredible ! Congratulations

The operative question is, how many of the 2M have we fixed?

(In reply to Frank Griffith Jr from comment #17)

The operative question is, how many of the 2M have we fixed?

I support finding the answer to this question.
Who should this be assigned to?

  • Bug 209558 - Mozilla burnt my laptop (with pictures)
    🪲🐛🪳🐞  BUGZILLA HITS 2,000,000!  🐞🪳🐛🪲

╔══════════════════════════════════════════════╗
║ 🪳🐛🪲 🐞🐛🪳🐞🐛🪲🐞 🪲🐛🪳 🐛🪳🐞🪲🐛🪳 ║
║ 🪲🐞🪳 🐛🪳🐞🪲🐛🪳🐞 🪳🐛🪲 🐞🪳🐛🪲🐞🪳 ║
║ 🐞🪲🐛 🪳🐞🪲🐛🪳🐞🪲 🐛🪳🐞 🪲🐞🪳🐛🪲🐞 ║
╚══════════════════════════════════════════════╝
🎉 TWO MILLION BUGS STRONG! 🎉
🐛 🐞 🪲 🪳 GOTTA SQUASH 'EM ALL! 🪳 🪲 🐞 🐛

(In reply to Frank Griffith Jr from comment #17)

The operative question is, how many of the 2M have we fixed?

Most of them: https://bugzilla.mozilla.org/reports.cgi?product=-All-&datasets=RESOLVED&datasets=VERIFIED

FIXED is a lower number, but if you're going to look at only that you need to subtract at least the DUPLICATE and INVALID bugs from the 2 million total or you get a very skewed picture.

It's impressive we have an issue/task management system that has been in operation for this long and has this many entries, and pretty much all of it in the open (I know there are exceptions for privacy and security reasons, but in general this is true). That underlines what this project is about.

Congratulations dear old friend.

See Also: → https://webcompat.com/

Not present in v146, but observable in current nightly. Does not crash the browser, but cause lot of emojis present all over.

Anyone care to guess how long it'll take us to get to bug 3000000?

The oldest bug on record seems to be bug 101, filed on 7 April 1998 (that's 891993290 seconds since epoch, according to the BMO timestamp).

We needed 871,055,940 seconds to get to bug 2000000 (filed at 1763049230 seconds since epoch, congrats :maxx!).

To start with the simplest model, interpolating between those two points and assuming linear growth, we're creating a new bug, on average, every (1763049230 - 891993290) / (2000000 - 101) = 435.5500 seconds, so we should get to bug 3000000 in another 435550000 seconds, or at (1763049230 + 435550000) = 2198599230 seconds since the epoch.

According to JavaScript, new Date(2198599230 * 1000) puts us at Friday, September 2, 2039, at 11:00:30 Pacific time (GMT-7) to reach our three millionth bug. 14 years to go!

Hope to see you all then for another celebration 🎉

🤣🤣🤣 Congrats!

YAY!!!!!!!!

(In reply to Jared Hirsch [:jhirsch] (he/him) (Needinfo please) from comment #25)

According to JavaScript, new Date(2198599230 * 1000) puts us at Friday, September 2, 2039, at 11:00:30 Pacific time (GMT-7) to reach our three millionth bug. 14 years to go!

That's quite a long time. I suggest a workaround, let's celebrate at 2222222.

(In reply to Jared Hirsch [:jhirsch] (he/him) (Needinfo please) from comment #25)

According to JavaScript, new Date(2198599230 * 1000) puts us at Friday, September 2, 2039, at 11:00:30 Pacific time (GMT-7) to reach our three millionth bug. 14 years to go!

I think that there is something wrong with the calculation. Bug 1.000.000 was filed 11 years ago. If we continue to expect a linear grows why it now should take us longer to reach bug 3.000.000? I don't think that the frequency of new bugs filed will drop but expect even an increase.

(In reply to Henrik Skupin [:whimboo][⌚️UTC+2] from comment #29)

(In reply to Jared Hirsch [:jhirsch] (he/him) (Needinfo please) from comment #25)

According to JavaScript, new Date(2198599230 * 1000) puts us at Friday, September 2, 2039, at 11:00:30 Pacific time (GMT-7) to reach our three millionth bug. 14 years to go!

I think that there is something wrong with the calculation. Bug 1.000.000 was filed 11 years ago. If we continue to expect a linear grows why it now should take us longer to reach bug 3.000.000? I don't think that the frequency of new bugs filed will drop but expect even an increase.

I decided to use the newly-supported Temporal API to double-check the calculations in the Firefox console, and Jared’s estimate was roughly correct given its starting assumptions. Here’s my code and output:

let b101date = Temporal.ZonedDateTime.from('1998-04-07T16:54[America/Los_Angeles]');
let b2MMdate = Temporal.ZonedDateTime.from('2025-11-13T07:53[America/Los_Angeles]');
let elapsed = Math.round(b2MMdate.since(b101date).total("seconds") * ((2000000 - 101) / 2000000));
console.log(b2MMdate.add(Temporal.Duration.from({seconds: elapsed})));

// 2039-09-07T15:59:40-07:00[America/Los_Angeles]

I changed the code to use your starting assumptions, and got:

let b1MMdate = Temporal.ZonedDateTime.from('2014-04-23T01:10[America/Los_Angeles]');
let b2MMdate = Temporal.ZonedDateTime.from('2025-11-13T07:53[America/Los_Angeles]');
let interval = b2MMdate.since(b1MMdate);
console.log(b2MMdate.add(Temporal.Duration.from(interval)));

// Temporal.ZonedDateTime 2037-06-05T16:36:00-07:00[America/Los_Angeles]

Either way, you end up in the late 2030s, which is indeed a while.

So I think we should accept Kai’s suggestion and celebrate bug #2222222, which a little more Temporal coding using your 1MM–2MM interval assumption tells me will happen on or about 2028-06-08T15:54:32-07:00[America/Los_Angeles]. Or we could mark bug #2345678 on or about 2029-11-11T21:24:40-08:00[America/Los_Angeles].

I thought a little more about this over the weekend 🤓

If anyone wanted to make a better guess at when we'll reach our next big milestone bug number (whether that's bug 2222222, or a power of 2, like bug 2097152, or a Fibonacci number, like bug 2178309), we could look at, say, every one hundred thousandth bug's creation date and use those to chart a more accurate linear (or other polynomial) regression. Here's a screenshot of a chart made using a spreadsheet tool with the slope and intercept listed in the legend.

(Since unfortunately I can't seem to add alt text to the screenshot here in BMO, I'll mention for those who can't see the screenshot that that the graph shows our bug filing velocity increased from bug 700k to about 1.7 million, and has since flattened out a bit. And the screenshot also shows the equation of the linear regression calculated by the spreadsheet tool, including all bugs, is y = 223*x - 257687, where x is the number of days since first bug and y is the estimated bug number we'll reach on that day.)

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: