Repository navigation
Repin to Solid 2.0.0-rc.19: zero recorded divergences - #9
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WjiThB5a8ekFuYHJXkD46h
…ain) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WjiThB5a8ekFuYHJXkD46h
All of Solid's fixes for our filed issues are on next. At 2c9fdd9 no scenario records a divergence on any runner. - DV-9, DV-15, DV-18 (and DV-10's one-effect mode): fixed upstream; the records in S-server-1, S-hold-5, S-solid-38, S-ai2-settings, S-server-3 and S-ai2-search are removed, and 05/10 and the repros README say so. - The ssr runner now runs Solid's production server build. With DV-9 fixed the server draws a failed boundary's fallback, and the development build keeps a panic's message by design; the production build sends the generic error SV-5b asks for (S-server-1). - DV-8's two leftover cases in S-ai2-search were ours: `pending? results` lowered to isPending(() => proj), and Solid's probe judges reads, not the return value (D-24, A23). `pending?` over a structured value now reads its keys (__rt.isPending in all three builds, the oracle's pending case). Repro: ref/oracle/repros/dv8b-projection-pending.mjs. interp 97/97, oracle 97/97, compiled 97/97 (0 divergences), ssr 90 pass 7 skip, types 135/135. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WjiThB5a8ekFuYHJXkD46h
ryansolid
pushed a commit
that referenced
this pull request
Oct 27, 2026
…T in #9) Checked against 2c9fdd9 with #9 merged locally: crate --lower 162/162 identical (630 maps), crate 280/280, RX_CRATE compiled 97/0 (0 divergences), ssr 90/0/7. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWMdD4K7882vob4J9vq
interp 97/97, oracle 97/97, compiled 97/97 (0 divergences), ssr 90 pass 7 skip, types 135/135. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WjiThB5a8ekFuYHJXkD46h
ryansolid
changed the title
ryansolid
pushed a commit
that referenced
this pull request
Oct 27, 2026
…OLID_NEXT in #9) With #9 merged: crate 280/280, --lower 162/162 (630 maps), RX_CRATE=1 compiled 97/0 with no divergences, ssr 90/0/7; compiler/test/vite.mjs 14 pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWMdD4K7882vob4J9vq
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WjiThB5a8ekFuYHJXkD46h # Conflicts: # ref/package.json
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WjiThB5a8ekFuYHJXkD46h
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Ryan · project thread
Every issue we filed against Solid is closed. This PR repins
ref/SOLID_NEXTto the 2.0.0-rc.19 release commit (nextd2323b0). On that commit, no scenario records a divergence on any runner. The first commit pinned2c9fdd9, thenextHEAD just before rc.19, and gave the same results.Results at rc.19 (
d2323b0), with main (#6) merged in: interp 97/97, oracle 97/97, compiled 97/97 (0 divergences), ssr 90 pass + 7 skip, types 135/135.Changes
--conditions=development). With DV-9 fixed, the server draws a failed boundary's fallback. Solid's development server build keeps a panic's message there by design. The production build sends the genericInternal Server Error, which is what SV-5b asks for (S-server-1 instant 2).pending? resultslowered toisPending(() => proj). Solid's probe judges the reads its thunk makes, never its return value, soisPending(() => store)isfalseby design (RULES-DERIVED D-24, A23).pending?over a structured value now reads its keys, in__rt.isPending(rt, rt-web, rt-server) and in the oracle'spendingcase. Repro:ref/oracle/repros/dv8b-projection-pending.mjs.Rust port: #6 is merged, and main's
compiler/Cargo.tomlalready pinsd2323b0, so the crate's Solid pin andref/SOLID_NEXTare equal once this lands. Theref/package.jsonconflict is resolved: it keeps this PR'sssrline and adds main'scrateandmodelscripts.The branch also carries an
-s oursmerge of this thread's earlier branch. That branch's README edits were already superseded on main, so the merge brings in no changes.🤖 Generated with Claude Code
https://claude.ai/code/session_01WjiThB5a8ekFuYHJXkD46h