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.
feat(console): report the running commit, and say which door failed (re-target of #152) #154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
feat(console): report the running commit, and say which door failed (re-target of #152) #154
Changes from all commits
b19a376b33b72e00224910159670File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the object API is unavailable during initial chat load,
fetchChatCatalog()hits/api/chat/projects, whose server catalog calls the same object seam and leavesloadErrorset after its 502 response. That branch then permanently wins over this disconnected branch and callsdegradationForwithout an origin, so the stable sidebar and main panel still discard the door, host, and status added by this change. Capture the catalog request's own origin rather than relying only on probe evidence.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: Travis-Gilbert/CommonPlace
Length of output: 8348
🏁 Script executed:
Repository: Travis-Gilbert/CommonPlace
Length of output: 15198
🏁 Script executed:
Repository: Travis-Gilbert/CommonPlace
Length of output: 24494
Render 403 workspace-refusal evidence when
connectionisidentity-refused.degradationForalready returns a 403 workspace-refusal detail, butChatPageonly passestransportOriginwhenconnection === 'disconnected'. Sincestatus === 403maps toidentity-refused, a 403 response from the transported request does not render the evidence banner. Includeconnection === 'identity-refused'in the same transport degradation branch.🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When connectivity fails after a chat has loaded,
threadandcatalogremain populated, so the sidebar selectsChatSidebarand the main panel selectsRuntimeTree; this newly added detail block is gated out by!thread. Those loaded-state components only show their existing generic unreachable messages, making the captured door and status invisible during the common mid-session outage scenario. Render or pass the degradation detail into the loaded-thread path as well.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟠 Major | 🏗️ Heavy lift
🧩 Analysis chain
🏁 Script executed:
Repository: Travis-Gilbert/CommonPlace
Length of output: 168
🏁 Script executed:
Repository: Travis-Gilbert/CommonPlace
Length of output: 477
🏁 Script executed:
Repository: Travis-Gilbert/CommonPlace
Length of output: 45538
🏁 Script executed:
Repository: Travis-Gilbert/CommonPlace
Length of output: 50382
Keep query-status failures from calling
console_data_api_unreachableagain.HttpBlockHostalready reports non-ok query responses through the constructor’sonStatus, including status and door.queryLiveWireandqueryLiveDomaincatch that thrown error, then report the same request asconsole_data_api_unreachablewith no status or origin, so 404/401/403/502 details are overwritten by the generic unreachable banner. Only emitconsole_data_api_unreachablewhen noonStatusstatus/origin was already reported, while still handling post-200 parse failures.🤖 Prompt for AI Agents
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.