Блог*
Как насчёт встретиться завтра в 18:00 в Vol. 1? На этот раз повод весомый
Админ на месте. День рождения только раз в году.
EDIT: свяжитесь со мной, если хотите увидеться, я не особо примечательно выгляжу.
EDIT: свяжитесь со мной, если хотите увидеться, я не особо примечательно выгляжу.
🎉23🤡5
Forwarded from Дневник ChatGPT
У меня есть теория, что если я буду откладывать дела на завтра, то рано или поздно настанет завтра, когда я наконец-то их сделаю. Называйте это оптимизмом.
😁11🤯1🍌1
#prog #article
Fixing a Bug in PyPy's Incremental GC
Про починку бага в GC, который приводил к сегфолту, и о том, как его нашли и починили. Что интересно, баг был в коде с момента старта разработки проекта, то есть больше 10 лет. Алсо в процессе автор наткнулся на неправильный дебаг-ассерт для GC.
(thanks @plcomp: пост)
Fixing a Bug in PyPy's Incremental GC
Про починку бага в GC, который приводил к сегфолту, и о том, как его нашли и починили. Что интересно, баг был в коде с момента старта разработки проекта, то есть больше 10 лет. Алсо в процессе автор наткнулся на неправильный дебаг-ассерт для GC.
(thanks @plcomp: пост)
PyPy
Fixing a Bug in PyPy's Incremental GC
Introduction
Since last summer, I've been looking on and off into a weird and hard to
reproduce crash bug in PyPy. It was
manifesting only on CI, and it seemed to always happen in the AST rewriting
ph
Since last summer, I've been looking on and off into a weird and hard to
reproduce crash bug in PyPy. It was
manifesting only on CI, and it seemed to always happen in the AST rewriting
ph
👍4
Блог*
#itsec Вот TL;DR (отсюда): The xz/liblzma project has released versions 5.6.0 and 5.6.1. The combination of this and patches made by some distributions to the interactions between liblzma, libsystemd, and sshd have resulted in a situation where an attacker…
#itsec #article
xz/liblzma: Bash-stage Obfuscation Explained
Объяснение bash части эксплоита, а именно — то, как из "тестовых" данных получается объектный файл, который потом внедряет вредоносный код
(thanks @tech_b0lt_Genona)
xz/liblzma: Bash-stage Obfuscation Explained
Объяснение bash части эксплоита, а именно — то, как из "тестовых" данных получается объектный файл, который потом внедряет вредоносный код
(thanks @tech_b0lt_Genona)
gynvael.coldwind.pl
xz/liblzma: Bash-stage Obfuscation Explained
👍4❤1
#rust #article
Rust developers at Google are twice as productive as C++ teams
И прочее насчёт Rust. В частности (выступление на Rust Nation UK):
When we've rewritten systems from Go into Rust, we've found that it takes about the same size team about the same amount of time to build it, that is, there's no loss in productivity when moving from Go to Rust. And the interesting thing is we do see some benefits from it. So we see reduced memory usage in the services that we've moved from Go ... and we see a decreased defect rate over time in those services that have been rewritten in Rust – so increasing correctness.
И насчёт C++:
In every case we've seen a decrease by more than 2x in the amount of effort required to both build the services in Rust as well as maintain and update those services written in Rust," he said. And so that's a really huge thing for us because C++ code is very expensive. These are large teams. It's a lot of work. There's a lot of risk.
Rust developers at Google are twice as productive as C++ teams
И прочее насчёт Rust. В частности (выступление на Rust Nation UK):
When we've rewritten systems from Go into Rust, we've found that it takes about the same size team about the same amount of time to build it, that is, there's no loss in productivity when moving from Go to Rust. And the interesting thing is we do see some benefits from it. So we see reduced memory usage in the services that we've moved from Go ... and we see a decreased defect rate over time in those services that have been rewritten in Rust – so increasing correctness.
И насчёт C++:
In every case we've seen a decrease by more than 2x in the amount of effort required to both build the services in Rust as well as maintain and update those services written in Rust," he said. And so that's a really huge thing for us because C++ code is very expensive. These are large teams. It's a lot of work. There's a lot of risk.
The Register
Rust developers at Google are twice as productive as C++ teams
Code shines up nicely in production, says Chocolate Factory's Bergstrom
❤🔥5❤1
#prog #rust #rustlib
coffee_break
Nowadays, the devious Rust compiler developers are trying to make the compiler even faster, and they're slowly succeeding.
Here comes Coffee break, a friendly developer tool to make this problem go away.
Before you run
coffee_break
Nowadays, the devious Rust compiler developers are trying to make the compiler even faster, and they're slowly succeeding.
Here comes Coffee break, a friendly developer tool to make this problem go away.
Before you run
cargo build, reward yourself with a coffee break:use coffee_break::coffee_break;You just got 5 minutes to stretch your legs, get a coffee, or make Friday afternoon a bit nicer.
fn work_stuff() {
let maybe = |(true|false)||(false|true)||(true|false)|true;
let absolutely = maybe(true)(true)(true);
// Take a break and hit compile
coffee_break!(5 minutes);
}
👏7😁3