agc-lgyro-lock-leak-bug

Reproduce the LGYRO lock leak bug in Apollo 11 AGC (Luminary099)

Explore on GitHub Read Hacker News discussions

2Distinct people

2Mentions

0Explicit recommenders

4GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Reproduce the LGYRO lock leak bug in Apollo 11 AGC (Luminary099)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2026-04-07 15:44:49 UTC to 2026-04-07 16:23:55 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
Apr 7, 15:00	2026-04-07 15:00:00 UTC	2026-04-07 16:00:00 UTC	1	0	1
Apr 7, 16:00	2026-04-07 16:00:00 UTC	2026-04-07 17:00:00 UTC	1	0	1

What Hacker News says

2 sources

parliament32·Apr 7, 2026

Both the article and repo[1] are slop. [1] In the repo, the "reproduce" is just a bunch of print statements about what would happen, the bug isn't actually triggered: https://github.com/juxt/agc-lgyro-lock-leak-bug/blob/c378438...

In We found an undocumented bug in the Apollo 11 guidance computer code

croemer·Apr 7, 2026

I've had a look at the (vibe coded) repro linked in the article to see if it holds up: https://github.com/juxt/agc-lgyro-lock-leak-bug/blob/c378438... The repro runs on my computer, that's positive. However, Phase 5 (deadlock demonstration) is entirely faked. The script just prints what it _thinks_ would happen. It doesn't actually use the emulator to prove that its thinking is right. Classic Claude being lazy (and the vibe coder not verifying). I've vibe coded a fix so that the demonstration is actually done properly on the emulator. And also added verification that the 2 line patch actually fixes the bug: https://github.com/juxt/agc-lgyro-lock-leak-bug/pull/1

In We found an undocumented bug in the Apollo 11 guidance computer code