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 16s

288 CI pipeline executions

Computation time saved

3d 5h

Cache hit rate

25%

Time to Green

9m 32s

Was 12m 7s, improved by 21%

Succeeded
11324
34171ce3 fix(solid-query): untrack the client read in useMutation's cache subscription useMutation subscribes to the mutation cache in the hook body via a bare client() memo read, which fires Solid's STRICT_READ_UNTRACKED diagnostic for any component that calls useMutation. Wrap it in untrack, matching how useBaseQuery guards the same body-scope read.
by Brenley Dueck
Succeeded
11292
daa90527 fix(solid-query): stand the client suspend down while hydrating Suspending a tracked data read while Solid is claiming server-rendered DOM (sharedConfig.hydrating) bails the claim: the server rendered this content from settled data that the streaming hydration channel may not have primed on the client yet, so the throw leaves unclaimed server nodes and crashes the reactive system with 'Potential Infinite Loop Detected'. Reads during the hydration window return the store value instead — exactly the pre-suspense behavior — and the per-query hydration coordinator re-syncs them once their entry lands. Reproduced in a fullstack streaming-SSR testbed (queries still in flight at hydration time): crashes on every affected load without the guard, zero errors across repeated loads with it. 329/329 package tests pass. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
11292
5ff20dde test(solid-query): drop the pendingData widening helper Rework the test call sites to sit closer to the non-nullable data contract instead of widening reads back to T | undefined: - Scalar displays read data naked ({state.data} renders empty while pending), including the persist-client provider test, which already read data naked everywhere else. Assertions on the removed 'null' fallbacks now match the bare label. - Snapshot captures push state.data directly. No test in the infinite file uses the reconcile option, so data is replaced rather than mutated in place and the JSON deep-copies were redundant. The useQuery reconcile test keeps its snapshot() capture, since in-place mutation is exactly what it asserts on. - Reads that dereference data (.pages, indexing) gate on isSuccess. On the client the proxy returns the raw store value, so a pending read is undefined at runtime and dereferencing it throws a TypeError that halts the reactive system - only the isServer branch routes through the query resource and throws NotReadyError. Reads already guarded by a Switch with a pending Match need no gate, since the fallback is never evaluated while pending. - suspense.test's render effect now tracks its spread in the compute function rather than reading state in the callback, clearing the STRICT_READ_UNTRACKED warnings that run emitted.
by Brenley Dueck
Canceled
11292
5ff20dde test(solid-query): drop the pendingData widening helper Rework the test call sites to sit closer to the non-nullable data contract instead of widening reads back to T | undefined: - Scalar displays read data naked ({state.data} renders empty while pending), including the persist-client provider test, which already read data naked everywhere else. Assertions on the removed 'null' fallbacks now match the bare label. - Snapshot captures push state.data directly. No test in the infinite file uses the reconcile option, so data is replaced rather than mutated in place and the JSON deep-copies were redundant. The useQuery reconcile test keeps its snapshot() capture, since in-place mutation is exactly what it asserts on. - Reads that dereference data (.pages, indexing) gate on isSuccess. On the client the proxy returns the raw store value, so a pending read is undefined at runtime and dereferencing it throws a TypeError that halts the reactive system - only the isServer branch routes through the query resource and throws NotReadyError. Reads already guarded by a Switch with a pending Match need no gate, since the fallback is never evaluated while pending. - suspense.test's render effect now tracks its spread in the compute function rather than reading state in the callback, clearing the STRICT_READ_UNTRACKED warnings that run emitted.
by Brenley Dueck
Succeeded
11292
936d5007 feat(solid-query): type useQuery/useInfiniteQuery data as non-nullable Reading data on a useQuery/useInfiniteQuery result is backed by an async resource that suspends the component into the nearest Loading boundary while the query loads, so by the time data is read during render it has settled. Reflect that in the types: data is TData, never undefined. - Add a distributive NonNullableData wrapper and apply it to UseBaseQueryResult and UseInfiniteQueryResult, keeping each status variant's other discriminants intact. - useQueries results are a plain reactive store with no resource backing (reads never suspend), so keep its data nullable via a local alias. - Update type tests for the new expectations, and widen intentional pending-state observations in runtime tests through a new pendingData test helper, which documents that those reads happen before the value exists at runtime.
by Brenley Dueck
Failed
11292
936d5007 feat(solid-query): type useQuery/useInfiniteQuery data as non-nullable Reading data on a useQuery/useInfiniteQuery result is backed by an async resource that suspends the component into the nearest Loading boundary while the query loads, so by the time data is read during render it has settled. Reflect that in the types: data is TData, never undefined. - Add a distributive NonNullableData wrapper and apply it to UseBaseQueryResult and UseInfiniteQueryResult, keeping each status variant's other discriminants intact. - useQueries results are a plain reactive store with no resource backing (reads never suspend), so keep its data nullable via a local alias. - Update type tests for the new expectations, and widen intentional pending-state observations in runtime tests through a new pendingData test helper, which documents that those reads happen before the value exists at runtime.
by Brenley Dueck
Succeeded
11292
936d5007 feat(solid-query): type useQuery/useInfiniteQuery data as non-nullable Reading data on a useQuery/useInfiniteQuery result is backed by an async resource that suspends the component into the nearest Loading boundary while the query loads, so by the time data is read during render it has settled. Reflect that in the types: data is TData, never undefined. - Add a distributive NonNullableData wrapper and apply it to UseBaseQueryResult and UseInfiniteQueryResult, keeping each status variant's other discriminants intact. - useQueries results are a plain reactive store with no resource backing (reads never suspend), so keep its data nullable via a local alias. - Update type tests for the new expectations, and widen intentional pending-state observations in runtime tests through a new pendingData test helper, which documents that those reads happen before the value exists at runtime.
by Brenley Dueck
Succeeded
fix/solid-suspense-background-refetch
8e4026bd Merge cb08a8fea3e99ec3694dc65c4277ae669815feb1 into b8e35598ef24855a2792414faea5721d833fa61e
by Brenley Dueck
Succeeded
solid-query-v6-pre
606d09d3 test(solid-query-devtools): stub devtools mount so the lazy UI import never starts The Test job failed post-merge with an EnvironmentTeardownError: mounting TanstackQueryDevtools(Panel) lazily imports the devtools UI, nothing in these synchronous tests awaits it, and on the slower CI agent the import was still in flight when vitest tore the environment down. Locally the import loses the race a different way: the UI chain pulls in @solid-primitives/transition-group, Solid 1 code that no longer resolves under this Solid 2 setup, surfacing as unhandled rejections. These tests only assert what the wrapper forwards to the instance, and the container element the style tests query is rendered by the wrapper itself, so mount() (and unmount(), which throws when nothing was really mounted) are stubbed in beforeEach. Rendered roots are now disposed via an explicit cleanup() before vi.restoreAllMocks(), because disposal calls unmount() and testing-library's automatic cleanup would otherwise run after the stub was already restored. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
11174
606d09d3 test(solid-query-devtools): stub devtools mount so the lazy UI import never starts The Test job failed post-merge with an EnvironmentTeardownError: mounting TanstackQueryDevtools(Panel) lazily imports the devtools UI, nothing in these synchronous tests awaits it, and on the slower CI agent the import was still in flight when vitest tore the environment down. Locally the import loses the race a different way: the UI chain pulls in @solid-primitives/transition-group, Solid 1 code that no longer resolves under this Solid 2 setup, surfacing as unhandled rejections. These tests only assert what the wrapper forwards to the instance, and the container element the style tests query is rendered by the wrapper itself, so mount() (and unmount(), which throws when nothing was really mounted) are stubbed in beforeEach. Rendered roots are now disposed via an explicit cleanup() before vi.restoreAllMocks(), because disposal calls unmount() and testing-library's automatic cleanup would otherwise run after the stub was already restored. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Failed
11174
9dbb8caf Merge branch 'solid-query-v6-pre' into chore/solid-v2-rc-main-merge Brings in #11175, the release bot's version commit, which turned the 6.0.0-rc sentinel into the real 6.0.0-rc.0 across the solid packages. One conflict, in examples/solid/offline/package.json, where each side was right about different lines: - @tanstack/query-async-storage-persister: kept our ^5.101.4, which comes from main and is part of what this branch delivers - @tanstack/solid-query*: took the base branch's ^6.0.0-rc.0 over our now-stale ^6.0.0-beta.8 references Verified after the merge: the three solid packages are on 6.0.0-rc.0 with no stale beta.8 references anywhere, the changelogs stay in descending version order across the rc/beta/5.101 boundary, and test:lib, test:types, test:build, test:eslint, sherif and knip all pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Failed
11174
7a980e1b Merge branch 'solid-query-v6-pre' into chore/solid-v2-rc-main-merge Brings in #11175, the release bot's version commit, which turned the 6.0.0-rc sentinel into the real 6.0.0-rc.0 across the solid packages. One conflict, in examples/solid/offline/package.json, where each side was right about different lines: - @tanstack/query-async-storage-persister: kept our ^5.101.4, which comes from main and is part of what this branch delivers - @tanstack/solid-query*: took the base branch's ^6.0.0-rc.0 over our now-stale ^6.0.0-beta.8 references Verified after the merge: the three solid packages are on 6.0.0-rc.0 with no stale beta.8 references anywhere, the changelogs stay in descending version order across the rc/beta/5.101 boundary, and test:lib, test:types, test:build, test:eslint, sherif and knip all pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
11174
2f3dd763 Merge branch 'solid-query-v6-pre' into chore/solid-v2-rc-main-merge Brings in the squash-merged #11173, which landed the solid v2 rc upgrade upstream. Two conflicts: - examples/solid/simple/package.json: kept our ^5.101.4 for @tanstack/eslint-plugin-query. The base branch still has ^5.101.0 because it has not taken main yet, and that bump is part of the main merge this branch delivers - pnpm-lock.yaml: regenerated from the merged manifests Verified after the merge: test:lib, test:types, test:build and test:eslint pass for all three solid packages, sherif and knip are clean, and the 6.0.0-rc sentinel matches what upstream now carries. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
solid-query-v6-pre
7b04d619 chore: upgrade to solid v2 rc, rename vite-plugin-solid, move branch to rc (#11173) - Bump solid-js, @solidjs/web, @solidjs/signals and babel-preset-solid 2.0.0-beta.33 -> ^2.0.0-rc.0 across the solid packages, the solid-vite integration and the solid examples, switching these from exact pins to carets so the rc line is picked up as it moves - Rename vite-plugin-solid -> @solidjs/vite-plugin ^3.0.0-next.27 (the version published under both names) in every manifest, vite config and the hydration test fixture; packages/query-devtools stays on vite-plugin-solid ^2.11.6 since it is still on solid 1.x - Drop the now-redundant `-i vite-plugin-solid` sherif ignore, since the dependency no longer resolves to more than one version - Raise the solid-query peer floor to >=2.0.0-rc.0 <3.0.0; the broader >=2.0.0-beta.0 floors on solid-query-devtools and solid-query-persist-client are left as they are - Switch the changesets prerelease tag from beta to rc, and set the solid package versions to the 6.0.0-rc sentinel so the next `changeset version` lands on 6.0.0-rc.0 rather than continuing the beta counter into 6.0.0-rc.9 - No source changes were needed; solid-query, solid-query-devtools and solid-query-persist-client pass unchanged (336 tests, no type errors), as do the solid-vite integration and solid example vite builds Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
11173
19c7623f chore: upgrade to solid v2 rc, rename vite-plugin-solid, move branch to rc - Bump solid-js, @solidjs/web, @solidjs/signals and babel-preset-solid 2.0.0-beta.33 -> ^2.0.0-rc.0 across the solid packages, the solid-vite integration and the solid examples, switching these from exact pins to carets so the rc line is picked up as it moves - Rename vite-plugin-solid -> @solidjs/vite-plugin ^3.0.0-next.27 (the version published under both names) in every manifest, vite config and the hydration test fixture; packages/query-devtools stays on vite-plugin-solid ^2.11.6 since it is still on solid 1.x - Drop the now-redundant `-i vite-plugin-solid` sherif ignore, since the dependency no longer resolves to more than one version - Raise the solid-query peer floor to >=2.0.0-rc.0 <3.0.0; the broader >=2.0.0-beta.0 floors on solid-query-devtools and solid-query-persist-client are left as they are - Switch the changesets prerelease tag from beta to rc, and set the solid package versions to the 6.0.0-rc sentinel so the next `changeset version` lands on 6.0.0-rc.0 rather than continuing the beta counter into 6.0.0-rc.9 - No source changes were needed; solid-query, solid-query-devtools and solid-query-persist-client pass unchanged (336 tests, no type errors), as do the solid-vite integration and solid example vite builds Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
solid-query-v6-pre
c6002fb5 chore: upgrade to solid v2 beta 29 (#11133) - Bump solid-js 2.0.0-beta.21 -> 2.0.0-beta.29, vite-plugin-solid 3.0.0-next.14 -> 3.0.0-next.21, plus matching @solidjs/web, babel-preset-solid, and @solidjs/signals bumps across the solid packages, solid-vite integration, and solid examples - No source changes were needed; the solid-query, solid-query-devtools, and solid-query-persist-client suites pass unchanged (357 tests, no type errors) Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
11133
f95a1c2b chore: upgrade to solid v2 beta 29 - Bump solid-js 2.0.0-beta.21 -> 2.0.0-beta.29, vite-plugin-solid 3.0.0-next.14 -> 3.0.0-next.21, plus matching @solidjs/web, babel-preset-solid, and @solidjs/signals bumps across the solid packages, solid-vite integration, and solid examples - No source changes were needed; the solid-query, solid-query-devtools, and solid-query-persist-client suites pass unchanged (357 tests, no type errors) Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
solid-query-v6-pre
dafe8066 chore: upgrade to solid v2 beta 21 (#11092) * chore: upgrade to solid v2 beta 21 - Bump solid-js 2.0.0-beta.15 -> 2.0.0-beta.21, vite-plugin-solid 3.0.0-next.5 -> 3.0.0-next.14, plus matching @solidjs/web and babel-preset-solid bumps across the solid packages, solid-vite integration, and solid examples - Add minimumReleaseAgeExclude for the Solid ecosystem packages so the freshly published betas install under the 24h release-age policy - Reset the reactive scheduler halt in solid-query-devtools test setup: the new betas permanently halt the scheduler when an error escapes all boundaries, which poisoned tests that follow intentional-throw tests in the same file Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * chore: add changeset for Solid beta 21 --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
by Brenley Dueck
Succeeded
11092
09094cfe chore: add changeset for Solid beta 21
by Brenley Dueck
Succeeded
11092
741e1bc5 chore: upgrade to solid v2 beta 21 - Bump solid-js 2.0.0-beta.15 -> 2.0.0-beta.21, vite-plugin-solid 3.0.0-next.5 -> 3.0.0-next.14, plus matching @solidjs/web and babel-preset-solid bumps across the solid packages, solid-vite integration, and solid examples - Add minimumReleaseAgeExclude for the Solid ecosystem packages so the freshly published betas install under the 24h release-age policy - Reset the reactive scheduler halt in solid-query-devtools test setup: the new betas permanently halt the scheduler when an error escapes all boundaries, which poisoned tests that follow intentional-throw tests in the same file Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Brenley Dueck