haha no source, just a dumb joke.

Japan: Checkmate

:: Reveals 10X more laws regulating game consoles ::

They’re probably all too busy working on Half Life 3

True polymorph is a hell of a drug.

I know, I know, it’s pronounced “Nyïmp”

Full name is GNUIMP anyway

Does Lemmy have a maps without New Zealand community?

🫳🏃‍➡️

We found a race condition in the teleport code. Turns out the efficiency curve for the restoration magic that undoes the disintegration in real time has a parabolic mana requirement related to mass, but disintegrate has a caterneric curve. For human sized stuff they match up, but if you try to teleport something of sufficient mass the restoration starts to draw a disproportionate amount of mana and the whole thing falls apart.

Also, we need to hire some more QA contractors.

Senior QA in the wizard world would actually be a respected title. Can’t make senior if you’re dead, and you can be alive if you’re bad at it.

2016->2019

wotc should pay dividends in unique rpg modules, then the shareholders get something cool noone else has.

🤓☝️.

If you’re worried about the veracity of the claims, I can assure you they’re true.

that’s amazing.

Unsolicited fact: Heinz picked the number 57 at random, it just sounded like good marketing at a time when things were general marketed as “tonic #4” and the like.

(well, maybe not fact, more like probable truth)

Distributed Honor-system Clothes Peg Server

A repo dedicated to non-unit-test tests would be the best way to go. No need to pollute your main code repo with orders of magnitude more code and junk than the actual application.

That said, from what I understand of the exploit, it could have been avoided by having packaging and testing run in different environments (I could be wrong here, I’ve only given the explanation a cursory look). The tests modified the code that got released. Tests rightly shouldn’t be constrained by other demands (like specific versions of libraries that may be shared between the test and build steps, for example), and the deploy/build step shouldn’t have to work around whatever side effects the tests might create. Containers are easy to spin up.

Keeping them separate helps. Sure, you could do folders on the same repo, but test repos are usually huge compared to code repos (in my experience) and it’s nicer to work with a repo that keeps its focus tight.

It’s comically dumb to assume all tests are equal and should absolutely live in the same repo as the code they test, when writing tests that function multiple codebases is trivial, necessary, and ubiquitous.

It’s not uncommon to keep example bad data around for regression to run against, and I imagine that’s not the only example in a compression library, but I’d definitely consider that a level of testing above unittests, and would not include it in the main repo. Tests that verify behavior at run time, either when interacting with the user, integrating with other software or services, or after being packaged, belong elsewhere. In summary, this is lazy.