PostgreSQL takes FOR UPDATE on rows before a DELETE, or before an UPDATE that modifies a column that is part of a unique index that neither contains expressions nor is partial
This also happens when you UPDATE the same row twice within the same transaction.
The Zig language accepts hard tabs and carriage returns. The self-hosted compiler implements the Zig language correctly; accepting hard tabs and carriage returns. However, the self-hosted compiler is not yet complete, and what people are using in reality is the stage1 compiler, which does not accept hard tabs.
You are confusing a layoff and a furlough. It's not your fault though, the Portuguese government decided to call a furlough a layoff for who knows what reason.