The account's line: Try now shows it tries, names what isn't answering, and one org's trouble holds no other - #53
Merged
Merged
Conversation
One organization's stalled or unread reads made the whole inventory read as loading, so every surface waited on data it never shows. The organization in view is now judged on its own reads: another organization's trouble changes nothing its consumers see, and with none chosen every one is in view.
…isn't answering Try now re-read what was in trouble and the line simply went, or stayed as it was, so it read as a no-op. It now says "Trying…" while it runs, keeps the line up while the organization's reads have not answered, and after 8 s says "Still not answering" with Try now again when they still have not. Under the sentence the line names what isn't answering: the organization's projects and services, or the one project when it alone is.
…provider The provider started Try now's 8 s timer, against the rule that it starts no timer. It now publishes only the account's trouble as facts — the lapse, the spoken trouble, whether the organization in view has answered, what isn't answering — and the actions; the line's own hook says "Trying…" and whether that helped.
fxck
added a commit
that referenced
this pull request
Oct 1, 2026
- #50 A person's own new project never waits on the path for someone else's - #51 A docked operation offers to open only when opening adds something - #52 A change's review reads the change itself, and rows name their repository when a Mate has two - #54 A coming-up Mate's page hands over as soon as the Mate answers, whatever the browser kept - #53 The account's line: Try now shows it tries, names what isn't answering, and one org's trouble holds no other - #56 The composer's top lists every change that waits for review - #55 A message echoed in the run card shows its words and its pictures - #57 One stalled subscription retries alone instead of replacing the organization's socket - #58 Docs: what the hours after 0.11.74 measured, and the fixes they took
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
1 participant
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.
The account's foot line "Zerops isn't answering. Trying again…" stayed up and Try now did nothing.
The lasting cause is the org socket's recovery stalling after a drop, with about 60 per-project subscriptions re-registered four at a time. It is fixed separately, by the move to org-wide reads.
This PR:
Tests: a six-row table for the per-organization loading, failed first; and the lapse and stalled-read provider tests, updated for the new Try now.
🤖 Generated with Claude Code