⚠ Satire · Every quote & number is real, every headline is editorialized · No maintainers were harmed ⚠

Season 1 · Episode 5 Saturday, November 7, 2026 · Vol. I, No. 5 Price: one clean project list

☕ Maintainer Tea

All the Drama That’s Fit to git blame

Episode 5 — “Root Access”

Codex users report a missing Projects list · ShareX users debate its new UI and AI disclosure · One workflow reports a broken action reference after a repository move · Trivy’s download domain returns

Developing

The Projects Have Left the Sidebar: Codex Users Report a Vanishing Act

A Windows user says Codex’s local project list disappeared after an app update and account switch; the folders and individual chats reportedly remained.

By Our Missing Projects Desk · Filed under accounts · local state

In openai/codex #59895, filed November 6, the reporter says local projects vanished after returning from an enterprise account to a personal one. Individual chats still appeared, and local folders still existed.

The reporter says an app update happened between a successful account switch and the failure, but does not establish that the update caused it. By November 7, the open issue had 20 comments and 9 reactions.

Commenters on Windows and macOS described similar symptoms, with mixed results: one said fully quitting and reopening restored projects; others said restarting did not. These are user reports, not an official fix. The issue remained open in this snapshot.

“Individual chats remain visible”
— the reporter on openai/codex #59895

More Drama Steeping

Hot Tea

ShareX’s UI and AI-Use Threads Ask Different Questions

One open issue asks for an option to return to the previous UI: ShareX #8952. Another asks the project to disclose AI use and alleges recent commits used AI: ShareX #8986. That claim belongs to the issue author; it is not independently confirmed.

As of November 7, #8952 had 65 reactions and 45 comments; #8986 had 36 reactions and 12 comments. Both threads remained open, with no project-member response in either thread at this snapshot. The comments include disagreement as well as support.

Drama Scalding
Developing

A Repository Move Leaves an Action Reference in Limbo

One workflow failed to resolve the old jlumbroso/free-disk-space action coordinates after the repository moved to an organization. The project owner said the transfer was to obtain Publisher Verification, reported that probes resolved the old references, and added a CI redirect canary.

Another reporter still saw “Repository not found” the next day. The issue remained open on November 7. free-disk-space #56 had 34 reactions and 3 comments.

Drama Spicy
Resolved

Trivy’s Download Address Drops Off the Map

A report says a cold-cache setup-trivy install failed when get.trivy.dev returned NXDOMAIN, so the download could not resolve. setup-trivy #42 had 60 reactions and 2 comments in the November 7 snapshot.

On November 5, a project contributor said the domain had an issue—not a breach or an attack—and that service was back. The issue is closed.

Drama Warm
Community Call

NixOS Starts a “Zero Hydra Failures” Campaign

NixOS release managers opened a call for help reducing Hydra build failures ahead of the planned November 30 release. Their initial post listed 4,391 failing builds across three platforms. That is the campaign’s starting figure, not today’s live total.

On November 7, NixOS/nixpkgs #584347 had 31 reactions and 5 comments; it invites contributors to find and fix broken packages.

Drama Warm
“Everything is up and running now.”
— project contributor on aquasecurity/setup-trivy #42, 3 reactions

The Status Desk · What Changed After the Reports

A November 7 snapshot of later replies. Counts are dated; workarounds are not official fixes.

Still Mixed

The Old Action Path Passed a Probe—Then Failed for Someone

The project owner said the old coordinates resolved in probes and added a CI redirect-canary. A different user still reported “Repository not found” the next day. The issue remains open; the thread does not establish a universal result.

34 reactions · 3 comments · open · free-disk-space #56

“the old coordinates resolve correctly again — verified twice.”
— the project owner in free-disk-space #56

Trivy’s Domain Came Back

A project contributor said the DNS problem was not a breach or an attack and that service was back on November 5. The issue is closed.

setup-trivy #42 · reply

One Unofficial Codex Workaround

One commenter said fully quitting and reopening restored projects for them. Other reports say restarting did not help. This is not a confirmed fix.

openai/codex #59895 · reply

ShareX’s AI-Use Claim Is Unverified

An issue author alleges recent commits used AI; the thread contains disagreement and support, but no project-member response in this snapshot.

ShareX #8986

The Back Page · Keep Steeping

The Real Steep Index

Ranked by reactions on each issue’s opening post, checked November 7—not by the full comment thread.

  1. 1ShareX #8952Option to use the previous UI65
  2. 2setup-trivy #42Download-domain DNS failure60
  3. 3ShareX #8986AI-use disclosure request36
  4. 4free-disk-space #56Action path after a repo transfer34
  5. 5openai/codex #59895Local projects missing from the list9

These five opening posts had 204 reactions in total. Reaction counts show attention, not agreement with a report or allegation.

The Flame War Index

Ranked by comment count: where people kept talking.

  1. 1ShareX #8952Old UI option request45
  2. 2openai/codex #59895Missing local project list20
  3. 3ShareX #8986AI-use disclosure request12
  4. 4free-disk-space #56Action path after a repo transfer3
  5. 5setup-trivy #42Download-domain DNS failure2

Comment counts are the GitHub snapshot from November 7. A longer thread is not proof that a claim is true.

The Week in Reactions

Reaction types on the five selected issue-opening posts, as checked November 7.

  • 👍197
  • 🚀2
  • 👀4
  • ❤️1

204 reactions across five selected posts. They show attention, not agreement with the underlying reports.

Comment of the Week

“Everything is up and running now.”

— project contributor · 3 reactions · setup-trivy #42

A crisp update after the reported download-domain problem. The same reply says it was not a breach or an attack.

Also This Week

Missed Connections

Fictional: You: the project list that vanished after an account switch. Me: the folders that stayed on disk. If you see this, your chats are still in Recents.

— The Missed Connections desk

Real Talk

“not a breach or an attack”

— a project contributor describing the Trivy download-domain issue. Source reply

  • The report says a cold-cache install could not resolve get.trivy.dev; the contributor said service was back on November 5. The issue is closed.
  • Keep the distinction clear: a user report described an installation failure; the later reply did not report a breach or an attack.

This update is based on the public issue and its follow-up, not an independent security investigation.

The Tea-Leaf Horoscope

Your week in open source, read in the tea leaves at the bottom of the CI logs. The horoscopes are fiction; the reporting above links to its sources.

♈ AriesMar 21–Apr 19

You will force-push to main on a Friday afternoon and call it decisiveness. The stars advise a rebase; your gut advises a merge. Your gut is not the one on call this weekend.

♉ TaurusApr 20–May 20

The dependency desperately wants to reach v3. You do not. Hold the line, Taurus: your pinned lockfile is a fortress, and refusing to upgrade is a love language.

♊ GeminiMay 21–Jun 20

You will approve the pull request, then leave four more comments after it has already merged. Two minds, one review thread, both of them somehow correct. Such is the Gemini way.

♋ CancerJun 21–Jul 22

A first-time contributor opens a trembling one-line PR. Be gentle, Cancer. You were a “typo in README” fix once, too, and someone let you merge it.

♌ LeoJul 23–Aug 22

Your changelog entry deserves top billing and you know it. Bask, Leo. Just remember the release notes are not technically about you. They are only a little about you.

♍ VirgoAug 23–Sep 22

Someone shipped it “good enough,” and you opened the diff anyway. The linter is your love letter, Virgo, and that trailing whitespace never stood a chance.

♎ LibraSep 23–Oct 22

Two valid approaches, equal and opposite, and the deciding vote is somehow yours. The “needs-discussion” label was invented for this exact Tuesday. Breathe.

♏ ScorpioOct 23–Nov 21

You will leave one “Requested changes,” no explanation, and watch the entire team spiral for a day. The bug is real, Scorpio. You simply enjoy the suspense.

♐ SagittariusNov 22–Dec 21

You called it a quick fix at 2 p.m. It is now a fourteen-file refactor and you regret nothing. Adventure is a Sagittarius value; so, it turns out, is the merge conflict.

♑ CapricornDec 22–Jan 19

“It stopped working and I changed nothing.” Something changed, Capricorn. It is always upstream, always a minor version bump, and never your fault. (It is sometimes your fault.)

♒ AquariusJan 20–Feb 18

You want the platform itself to do the right thing so nobody else has to. Noble, Aquarius. The spec should land in roughly a decade, so pack a snack and a polyfill.

♓ PiscesFeb 19–Mar 20

Your notification badge has reached a number that is no longer technically a number. Swim away if you must, Pisces, but the flaky test will still be failing when you surface.