Overview - Query

queryWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

query

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

queryWorkspace

Average execution time

4m 12s

306 CI pipeline executions

Computation time saved

3d 5h

Cache hit rate

25%

Time to Green

9m 17s

Was 11m 52s, improved by 22%

Succeeded
11357
b50b7bdc test(solid-query): pin the stale read through a memo over query.data A tracked computation that reaches a leaf THROUGH a `createMemo(() => query.data)` indirection is not re-notified after a refetch, so its last observation stays the superseded value permanently. A wrapper hook that gates or narrows `query.data` before handing it to consumers is exactly this shape, so it reaches app code that never writes the memo explicitly. The data node is not at fault: the derive runs the expected number of times, the commit lands, the DOM swaps, and an untracked read through the very same memo returns the new value. Every other reader shape is notified correctly, and the behaviour reproduces with no TanStack code involved, so the test is skipped pending the upstream fix in solidjs/solid#3181. Refs #11351 Co-authored-by: Cursor <cursoragent@cursor.com>
by Mauro Garcia
M