Overview - Query

7 days30 days

Latest CI Pipeline Executions

Fuzzy

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