D:\a\swift-url\swift-url\.build\checkouts\swift-system\Sources\System\FileOperations.swift:445:7: error: cannot find 'system_ftruncate' in scope
I don't like it when my builds break because
swift-system published a release without even testing it. Please never do that again.
Sometimes, despite your best efforts, things don't work. That's life. But when basic stuff - really, completely novice-level, first-day-of-coding best practices are not followed, then I think it is correct to start pointing the finger, dispensing anger and attributing blame. At that point, it's not an accident, it's recklessness.
lack of regard for the danger or consequences of one's actions; rashness.
I don't care that a commit was merged without tests passing; that happens all the time. But the reason that we have releases as a separate thing from branches is because there is an enhanced presumption that releases will work. The fact this went the extra step - in to a release - without testing - is mind-blowing
A junior engineer would be embarrassed by that, let alone a package published under Apple's name and maintained by Apple's staff of professional engineers.
Sorry if this seems harsh, but this is an exceptionally poor situation, and I consider it appropriate that those responsible feel fingers and anger directed towards them. Honestly - I would think twice about a junior engineer who showed this kind of abandon and published releases without testing. It's not good enough.
EDIT: No, I don’t think this is inappropriate or worth flagging. The package maintainers are showing a reckless disregard for those who depend on the Windows release and their feet should be held to the fire about it.
We need to have a talk about why this keeps happening. The priority shouldn’t be to shield people from criticism.