She who made bugs @ariasuni@mastodon.technology

2 warnings generated.
make[2]: *** [/home/ariasuni/projets/mozilla-central/config/recurse.mk:34 : compile] Erreur 2
make[1]: *** [/home/ariasuni/projets/mozilla-central/config/rules.mk:423 : default] Erreur 2
make: *** [client.mk:151 : build] Erreur 2
compiler warnings present.

And then the build fails. WHAT

❯ hg bisect --good 432940:d77ca862636d
abort: unknown revision '9b933ffa7e4455563b74121da75047a4e7eb12a6'!

But what the fucking fuck.

❯ hg bisect --good
aborting: inconsistent state, 431548:b712d41d4745 is good and bad

OK I made a mistake and now I can’t go back?? wtf

Well turns out I had to install an old version of cbindgen and link it to `/usr/bin/cbindgen`. It feels good to be able to fix the problems without too much trouble, but damn it is so annoying to have in the first place.

Turns out compiling software from 1 year and a half ago on Arch Linux is annoying. New kernel versions, new Glibc versions, new utilities installed on the system…

Treating warning as errors will break stuff for people.

https://bugzilla.mozilla.org/show_bug.cgi?id=1519629

Fortunately, it’s easy to switch the Rust compiler to an older version, I just had to use `rustup default 1.32.0` and here we go

`error: missing documentation for macro`

oh my god I’m gonna punch something

I thought Linux wasn’t breaking userland but apparently it does.

tfw after 30 minutes of compilation I get an `error: use of undeclared identifier 'SIOCGSTAMP'` and then I try to figure out with a search engine what the fuck, and then I find the commit that fixed it for later versions that I will need to apply (probably shelve and unshelve — stash and stash pop in git parlance — at each commit I test).
https://hg.mozilla.org/mozilla-central/rev/49be991ad4d9

It seems that most compilation errors go away after doing `./mach clobber` but then you have to do a full compilation from scratch which is very long, even with my modern computer and ccache.

I needed ~10 tests for your bisect, and it took like several days of figuring out the errors and compiling and getting distracted while it compiled.

And now here I am, doing a new bisect, with my `88460 changesets remaining, ~16 tests`. Damn it.

I’m trying to compile “old” (2018) versions of Firefox to find which commit introduced a bug.

This is… not fun.

Not pre-built artifacts since it’s too old.
Compilation errors because glibc’s too recent.
Make errors (make: *** No rule to make target […])
Compilation errors that comes from nowhere, too.

Uh why Font Awesome icons have their size set to 1.28571429em by default??

«The excel class defines the usual properties of an Excel-generated CSV file. It is registered with the dialect name 'excel'.»

What are «the usual properties of an Excel-generated CSV file»? Is this even documentation?? Could use a little bit more precision there.

I need unit tests so bad for my project but why is it so hard. Isn’t the web the most used damn platform? Why does testing my WebExtensions feels like I’m doing a daunting, impossible task nobody has ever undertook?

Yeah I wanted to give up on unit tests but then I broke some things again and I’m tired of manually testing things. I just want to actually progress, not fight forever with unit tests or break things all the time.

How am I supposed to use jest mocks and JSDOM for unit tests?

Somehow I can’t manage to properly isolate each test. When I simulate a click on an element, listeners set up in each previous test are triggered…

It’s not really hard to handle all this stuff, but the great amount of packages and the npm UI tend to make it confusing sometimes. But it’s hard so screw up something like it could happen with git so I guess it’s fine.

Anyway I’ve “20 low severity vulnerabilities in 1112084 scanned packages” I can’t do anything about now but it’s only development packages so I don’t care I guess, my packages are as up-to-date as they can be.

Please understand that’s only two (2) packages, acorn and minimist, but duplicated as a dependency of hundreds of packages. Obviously I don’t fucking care but somehow it’s important to spam my terminal with hundreds of lines of telling the same package is vulnerable.

me: let’s update a dev dependency of my addon
npm: found 38460 vulnerabilities (38441 low, 19 moderate)

Please upvote if you think it deserves to appear in first position ^^