@lritter If done right, these can be great for your indoor environment - switching up the material you place behind those bars.
Installing the bars without taking advantage of that does seem pretty silly.
Got to take JetBrains Space for a spin. Promising so far.
Early days for sure - particularly on the configuration documentation front, but got it running via a podman install on NixOS, mirroring a gitea repository.
Not quite interfacing with our existing JetBrains Hub install yet. Very much looking forward to the availability of the YouTrack and TeamCity integrations.
Looks to generally carry through the YouTrack design of flexible data design, but with another UX step-up.
@Tak You manage some of the most interesting explosions :)
Like fireworks - good to watch at a distance - not necessarily at ground zero.
@aras Though you probably don't have to look _super_ hard to find some business trying to profile itself as both sustainable _and_ involved in selling you NFTs to something in some metaverse ;)
"New Gear": An overview of changes to my active toolbox over the last couple of years:
@Tak Relax - it's not that old.
That's just when it was reported on github. The bug itself is way older.
Hypervisor workstation horrors:
Today I learned why recently my primary workstation VM would just die on me from time to time:
Had forgotten to actively set up swap for the hypervisor and had recently increased overall system memory pressure. So whenever I hit the memory ceiling, the memory manager would kill the hungriest process - easily the qemu process for my main workstation VM.
@sirdimples Some platform is always dying in someones personal optics ;)
Personally I arrived at the opposite end of the spectrum: After ages of working from laptops I'm pretty sure the 2013 model I retired a couple of years ago will be my last for a long time.
@thendrix It sounds like there might be some hope in some future release of the package: Decoupling the runner and the framework.
For one it would allow us to run xUnit, but it would also free up utech team resources to focus on the runner.
- #Unity will ignore the -executeMethod flag when the -runEditorTests flag is also passed.
- The #Unity test runner _does_ wait for completion of other domain load invokes, including invoked script reloads, before responding to -executeMethod.
So: If you want to parameterise a TC Unity test run, use custom CLI parameters.
@Tak Mostly I was just reminded of the atomic system updates in the context of your rainy day story ;)
TIL: Unlike other targets (including the editor mono JIT), #unity IL2CPP very much does not like it when you keep things in the stack for later.
LD, DUP, OP, OP
LD, OP, LD, OP
Handling of the unfortunate case is _not_ very graceful: Nonsensical generated C++. Thankfully it at least doesn’t compile.