Then I would suggest checking if you have filament g-code set in your slicer, I guess it's possible the z-stop was calibrated with a z-offset applied, and when it was removed by setting PLA the nozzle tried to go slightly below 0. What firmware are you running?
From the pic it looks almost like the first layer is still on the plate, or is it etched on? I doubt it's the latter or your nozzle would be completely obliterated (and it would've made a god-awful noise the entire time). Sorry for the dumb question but, are you sure it's not just filament with incredibly strong adhesion? Does it stop a scraper if you hit an edge?
To answer your question, yes usually PETG is printed with a slight positive offset so the filament is deposited instead of squished. Something like 1/4 of the nozzle diameter
The Codex TUI has a similar bug where a useless animation costs way too many resources, but it's definitely a different area of code. It was originally redrawing the entire TUI screen every 32ms. That one has a Codex-created fix, but user PR's aren't considered anymore. It was originally memory leaking 20GB (!) over 2-3 days
Jack seems like a pretty cool dude from what I've seen of him. Maybe he had some fumbles but from what I can tell he really is well intentioned. He does care about his fellow artists a lot
The KPMG report, initially flagged by the Register, surveyed 2,145 senior execs across 20 countries, finding that an astonishing 29 percent of them had no idea where the growing costs associated with AI were coming from.
Why did you release alpha 6.0.6 then 6.0.1 beta? And how are you on 6.x for an unreleased hobby project started this year anyway? And why are they in different repositories?
What's oniony about this?