You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
No loading, error, or degraded states: failed data loads leave an empty map and SYS NOMINAL #10
Related degraded state found while fixing #8 (PR #20): RENDER now comes from deck.gl's onDeviceInitialized callback (src/components/MapView.jsx, DeckGLOverlay). If deck fails to create a device, RENDER stays Detecting... forever, and after a lost WebGL context it still shows WebGL2. This fits this issue's "header status reflects actual app health" goal. Suggested addition to the acceptance criteria: a render-device failure or context loss shows an error state in the GPU panel (for example RENDER Failed) and makes the header status DEGRADED.
Another silent failure, found while fixing #15 (PR #21): if the heatmap WGSL fails to compile or the pipeline is invalid, useGPUHeatmap (src/hooks/useGPUHeatmap.js, the compute section after createShaderModule) still reports success, so an empty heatmap is drawn and the toggle shows ON. WebGPU validation errors are asynchronous, so they need pushErrorScope('validation') / popErrorScope() or getCompilationInfo(); useGPUCompute already does this after #11. Suggested addition to the acceptance criteria: a heatmap compute failure, including a shader or pipeline validation error, shows the heatmap layer as failed, not as loaded.
Activity
GeoBradDev commentedon Nov 8, 2026
Related degraded state found while fixing #8 (PR #20): RENDER now comes from deck.gl's
onDeviceInitializedcallback (src/components/MapView.jsx,DeckGLOverlay). If deck fails to create a device, RENDER staysDetecting...forever, and after a lost WebGL context it still showsWebGL2. This fits this issue's "header status reflects actual app health" goal. Suggested addition to the acceptance criteria: a render-device failure or context loss shows an error state in the GPU panel (for example RENDERFailed) and makes the header status DEGRADED.GeoBradDev commentedon Nov 8, 2026
Another silent failure, found while fixing #15 (PR #21): if the heatmap WGSL fails to compile or the pipeline is invalid,
useGPUHeatmap(src/hooks/useGPUHeatmap.js, the compute section aftercreateShaderModule) still reports success, so an empty heatmap is drawn and the toggle shows ON. WebGPU validation errors are asynchronous, so they needpushErrorScope('validation')/popErrorScope()orgetCompilationInfo();useGPUComputealready does this after #11. Suggested addition to the acceptance criteria: a heatmap compute failure, including a shader or pipeline validation error, shows the heatmap layer as failed, not as loaded.Merge pull request #22 from GeoBradDev/issue-10-loading-error-degrade…