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

7m 24s

418 CI pipeline executions

Computation time saved

3d 19h

Cache hit rate

26%

Time to Green

24m 5s

Was 26m 9s, improved by 8%

Succeeded
11543
24d8bfee fix(solid-query): follow Solid 2.0.0-rc.9 Build with @solidjs/babel-plugin (the Solid 2.0 compiler; rc.9 moved delegated handlers to the `_$$` key, so the compiled output must match the runtime), test under vite 8 for the Solid packages, examples and the vite integration (scoped overrides; @solidjs/vite-plugin next.32+ needs vite ^8), and raise the solid-js / @solidjs/web peer floor to rc.9. useQuery: setup-time snapshots (meta projection seed, mount counts) read the cache through lookupQuery() instead of query(), which reads the version signal. Under hydration, priming writes that signal during setup and Solid holds a write made during the pass: a computation in the pass that reads it is served the pre-write value and replays at release. For the hook's derived nodes that is the takeover; for the computation instantiating the component (a <Loading> boundary's children) it was a remount that re-created the hydrated component as a client render, so cache writes reached the DOM while the stream was open. Tests: four assertions adapted to rc.9's committed-frame model (a write becomes visible at flush, to every channel): status/isPending read the held frame mid-hold, isFetching is the pending probe; the mutation settle commits fresh data and the lifted overlay in one frame. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
by Ryan Carniato
R