Graph-Native Infrastructure for Context and Accountable AI Systems
Python agent-memoryaiai-governanceai-infrastructureartificial-intelligencecontext-engineeringcontext-graphsdata-engineeringdecision-intelligencedeveloper-toolsexplainable-aigenerative-aigraph-ragknowledge-graphllmontologyprovenancepythonreasoningsemantic-search
Fix remaining silent-failure gaps flagged in review of #790
KaifAhmad199b0a517fdbe
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 263f02f0..073ccac8 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -11,7 +11,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0### Fixed-- **Explorer backend routes returned HTTP 200 with error/empty bodies on failure, defeating frontend error handling** (#770, #787) by @Sameer6305 and @KaifAhmad1+- **Explorer frontend workspaces silently swallowed network/server errors** (#767, #790) by @Sameer6305+ - `ShaclStudio.tsx`, `VersionsTab.tsx`, `SKOSVocabularyManager.tsx`, `EntityResolutionTab.tsx`, `LineageDiagram.tsx`, `DecisionWorkspace.tsx`, `KGOverviewTab.tsx`, `OntologyManager.tsx`, `OntologySearch.tsx`, `ReasoningWorkspace.tsx`, and `SparqlWorkspace.tsx` now render a visible error banner instead of only `console.error()`-ing failed fetches+ - Added explicit `response.status === 207` (Multi-Status) handling across these workspaces so partial backend failures surface a warning instead of reading as a full success (`response.ok` is `true` for all 2xx codes, including 207)+ - Added defensive JSON parsing so an unexpected non-JSON (e.g. HTML 500) response body no longer crashes the app with `SyntaxError: Unexpected token < in JSON`+ - Fixed `KGOverviewTab.tsx` dropping the `/api/graph/nodes` partial-success warning whenever `/api/graph/stats` also returned 207 — both warnings are now shown (appended) instead of one being silently discarded+ - Fixed `HealthTab.tsx`'s registry load still using a bare `.catch(() => {})` that swallowed errors identically to the pattern fixed elsewhere in this same folder; failures now populate the existing error banner+ - Fixed `AlignmentsTab.tsx`'s `reload()` using `Promise.allSettled` but never handling the `"rejected"` branches for the registry/alignments fetches, so both failures previously vanished with no error surfaced and no logging- `GET /api/temporal/patterns` now raises `HTTPException(500)` on a genuine computation failure instead of silently returning an empty-but-valid `TemporalPatternResponse`; the `ImportError` fallback (optional `kg` extra not installed) is unchanged and still degrades gracefully to an empty list- `POST /api/ontology/create` now raises `HTTPException(500)` when ontology generation fails in either the `sample_data` or `schema_text` mode, instead of silently falling back to a partial/minimal ontology with a misleading `nodes_added` count- `GET /api/analytics` sets `response.status_code = 207` (Multi-Status) when some, but not all, of the requested metrics fail, and raises `HTTPException(500)` when every requested metric fails — a plain 2xx (including 207) reads as success to callers that only check `response.ok`, so an all-failed request now surfaces as a hard error rather than a body full of `{"error": ...}`diff --git a/explorer/src/workspaces/ManageWorkspace/KGOverviewTab.tsx b/explorer/src/workspaces/ManageWorkspace/KGOverviewTab.tsxindex 33746269..92410fd5 100644--- a/explorer/src/workspaces/ManageWorkspace/KGOverviewTab.tsx+++ b/explorer/src/workspaces/ManageWorkspace/KGOverviewTab.tsx@@ -93,8 +93,9 @@ export function KGOverviewTab() {const nodesData: NodeListResponse = await nodesRes.json();const nodes = nodesData.nodes ?? [];setNodeTypeMap(buildTypeMap(nodes, "type"));- if (nodesRes.status === 207 && statsRes.status !== 207) { // Only overwrite error if not already set, or just append- setError((prev) => prev ? prev + " " + ((nodesData as any).message || "") : ((nodesData as any).message || "Warning: Partial success loading nodes."));+ if (nodesRes.status === 207) {+ const nodesMessage = (nodesData as any).message || "Warning: Partial success loading nodes.";+ setError((prev) => (prev ? `${prev} ${nodesMessage}` : nodesMessage));}// Simulate neighbor counts via edges fetch for top-Ndiff --git a/explorer/src/workspaces/OntologyWorkspace/AlignmentsTab.tsx b/explorer/src/workspaces/OntologyWorkspace/AlignmentsTab.tsxindex 8034705d..8790787d 100644--- a/explorer/src/workspaces/OntologyWorkspace/AlignmentsTab.tsx+++ b/explorer/src/workspaces/OntologyWorkspace/AlignmentsTab.tsx@@ -54,15 +54,20 @@ export function AlignmentsTab() {loadAlignments(),]);+ const errors: string[] = [];if (registryResult.status === "fulfilled") {setRegistry(registryResult.value);setSourceOntology((current) => current || registryResult.value[0]?.uri || "");setTargetOntology((current) => current || registryResult.value[1]?.uri || registryResult.value[0]?.uri || "");+ } else {+ errors.push(registryResult.reason instanceof Error ? registryResult.reason.message : "Failed to load ontology registry.");}if (alignmentResult.status === "fulfilled") {setAlignments(alignmentResult.value);+ } else {+ errors.push(alignmentResult.reason instanceof Error ? alignmentResult.reason.message : "Failed to load alignments.");}-+ if (errors.length) setError(errors.join(" "));}, []);useEffect(() => {diff --git a/explorer/src/workspaces/OntologyWorkspace/HealthTab.tsx b/explorer/src/workspaces/OntologyWorkspace/HealthTab.tsxindex 44d2ffed..47e27dea 100644--- a/explorer/src/workspaces/OntologyWorkspace/HealthTab.tsx+++ b/explorer/src/workspaces/OntologyWorkspace/HealthTab.tsx@@ -23,7 +23,10 @@ export function HealthTab({ onFixInEditor }: HealthTabProps) {setRegistry(entries);setSelectedUri((current) => current || entries[0]?.uri || "");})- .catch(() => { /* backend unavailable — leave registry empty */ });+ .catch((err) => {+ if (cancelled) return;+ setError(err instanceof Error ? err.message : "Failed to load ontology registry.");+ });return () => {cancelled = true;};