Add ISSUE-040 and ISSUE-041 to the backlog - #52
Merged
Sellafield merged 1 commit intoAug 17, 2026
Conversation
Two defects reported by the lead developer on Discord on 2026-08-15, neither of which had an entry: - ISSUE-040: assembled robots stored in corporation hangars at PBS bases are altered by a server restart, known internally as the "Peanut Plague" - ISSUE-041: characters stay online after the player logs out and closes the client Neither is reproduced in a development environment. Both entries record what is known, what is not, and where an investigation would start; every line number they cite was checked against 4e6d697 and is anchored to it. ISSUE-041 is filed separately from ISSUE-038 rather than folded into it. ISSUE-038 documents the same ghost-session mechanism, but it closes on a memory measurement, while the visible-online symptom is what players report. ISSUE-038 also deferred an application-level idle timeout pending "real-world observation" -- this report supplies that observation. The entry also records a detail that does not fit: the documented keepalive mechanism explains ungraceful disconnects, while the report describes a clean logout. Both entries carry a Tracking line pointing at their GitHub issue, so the file stays the record and the issue carries the discussion. Last ID used goes from 039 to 041. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds two backlog entries for defects reported on Discord on 2026-08-15. Neither had an entry in
docs/backlog/, and the first has no record anywhere in the repository.One file changed. No code.
ISSUE-040— assembled robots in corporation hangars at PBS bases are altered by a server restart ("Peanut Plague")ISSUE-041— characters stay online after the player logs out and closes the client ("zombie sessions")Last ID usedgoes from 039 to 041.What these entries do and do not claim
Neither defect is reproduced here. Both entries say so in their first paragraph, and neither proposes a fix ahead of an investigation — the first step in each is to establish what is actually happening. What they add on top of the report is the set of code anchors an investigation would start from, and every line number cited was checked against
4e6d697rather than carried over from older notes.The priorities — HIGH for
ISSUE-040, MEDIUM forISSUE-041— are a judgement made when filing, since the report assigned none. Both entries say that in their Notes. Overrule either freely.Why
ISSUE-041is separate fromISSUE-038ISSUE-038already documents the ghost-session mechanism in detail:TcpConnectionsets the OS-level TCP keepalive, and it is the only backstop for a peer that disappears without a clean close, since there is no application-level heartbeat. It shipped a mitigation (keepalive 24h to 2h, live today) and explicitly deferred an application-level idle timeout, recording that it was "offered as an option" and not requested, and "worth reconsidering if 2h keepalive still isn't tight enough after real-world observation."That observation has now been reported, so the deferral is due for review. It is a separate entry rather than an addition to
ISSUE-038becauseISSUE-038is about memory growth and would close on a memory measurement, while players report the visible-online symptom and that needs to outlive the memory issue.One detail in the report does not fit the documented mechanism, and the entry says so instead of smoothing it over. The keepalive story explains ungraceful disconnects — crashes, dropped networks, closed laptop lids. The report describes a clean exit: logged out, closed the client. If clean logouts really are affected, the teardown path itself is at fault and the idle timeout would not fix it. Separating those two cases is step 1 in the entry, ahead of any change.
On the duplication with #50 and #51
Each entry carries a
Tracking:line pointing at its issue. The intent is that the file stays the record — greppable, diffable, citable from a commit — and the issue carries the discussion and shows who has picked the work up. If you would rather these lived in only one of the two places, say which and it is a small change.