imbajin opened a new pull request, #837:
URL: https://github.com/apache/hugegraph-toolchain/pull/837

   Cluster alerts could lead to an empty or filtered node list without 
explaining the failure, and a Store source could show a green UP badge 
alongside partial or failed collection. This change links alerts to source 
diagnostics independent of table pagination or filters, including when 
discovery produces no nodes, showing the failed request path, HTTP status, 
bounded response size/limit, freshness, last success and affected metric groups.
   
   Source badges now consider collection availability and stale data. Metric 
transport failures retain PD-reported node status rather than inventing DOWN; 
explicit node refresh bypasses the snapshot cache. Generated Server names use 
`Server`, while custom names and stable IDs are preserved. Diagnostic metadata 
excludes hosts, query strings, credentials, response bodies and raw exception 
messages; response limits and target trust rules remain in place.
   
   Unsupported metric groups retain their failure details when a source is 
partial, malformed responses include their request path, and confirmed DOWN or 
DEGRADED topology takes precedence over unsupported metrics in source badges, 
attention alerts and overall health.
   
   Rejected DNS resolutions and malformed Store REST addresses retain their 
safe request paths. Failure summaries and diagnostic rows include genuine 
unsupported endpoint failures while excluding uncollected/topology 
placeholders, and an initial snapshot load failure no longer fabricates an 
UNKNOWN source panel.
   
   Validation: the final diagnostics increment passed 81 backend and 37 
frontend tests, ESLint and whitespace checks. Chrome authenticated/anonymous 
API fixtures verified initial-load failure without a fabricated panel, healthy 
refresh recovery, diagnostics, GraphSpace context switching and account 
visibility. Earlier TypeScript, i18n and Vite production build checks passed. 
README screenshots identify the API fixtures; live Server/PD/Store connectivity 
and enforcement remain unverified.
   
   Tracks Issues 5–8 in the [Hubble issue 
record](https://chatgpt.com/space/page_62cf6a23a284819196000f124fdd6990). Kept 
separate from GraphSpace PR #81 because this is an independent Operations 
change exceeding 500 lines, including regression tests and diagnostic UI. 
Additional API health contract fixes are in stacked PR #83, which depends on 
this PR. Readiness probes remain a separate follow-up.
   
   CI tooling: run the frontend-notice generator's pnpm subprocesses from the 
frontend directory so Corepack selects its pinned version. Its regression is 
wired into CI; full notice regeneration produced no artifact changes.
   
   ---
   
   ## Upstream submission notes
   
   Source community PR: 
https://github.com/hugegraph/hugegraph-toolchain/pull/82. This upstream PR 
reuses the same source repository and branch. Validation statements above are 
reports from the source task; they were not independently rerun during upstream 
submission. At submission preflight, source-head hosted checks: 1 neutral, 5 
skipped, 22 success. Upstream exact-head CI and current review feedback require 
separate confirmation; opening this PR does not establish merge or release 
readiness.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to