Skip to content

Solid v2.0.0-beta.10 refresh() does not catch NotReadyError #2694

Closed

Description

@atk

Describe the bug

Calling refresh(optimistic) throws an error that comes from a NotReadyError from calling count() that should have been filtered out.

Your Example Website or App

https://solid2.netlify.app/#solidjs-repl:X5S967tfRauLNiWUdm43Jw

Steps to Reproduce the Bug or Issue

  1. Go to the page
  2. Cllck on the button
  3. Check error in console

Expected behavior

NotReadyError should be filtered out

Screenshots or Videos

No response

Platform

  • OS: aarch64 Linux
  • Browser: Chromium
  • Version: 147.0.7727.101

Additional context

No response

Activity

  1. ryansolid commented on May 11, 2026

    @ryansolid
    Member

    We fixed this but also changed its shape.. refresh only takes direct refreshable things like accessors/stores.. This required branded types that I'm not stoked about but it seems to work well enough: Fixed in beta.11

  2. atk commented on May 12, 2026

    @atk
    ContributorAuthor

    The exact same example run with beta.11 unfortunately still shows the exact same error if I click on the button.

  3. mizulu commented on May 12, 2026

    @mizulu

    @atk if you are basing the reproduction based on the
    old playground then it is still failing because it does not use the correct @solidjs/signals version

    it is better to use the playground in the new domain https://s.olid.uk
    it has much better for version pinning, and has features to show when version mismatches exists
    I did not update the netlifty one as to not impact old bug reports, but new bugs should use the newer maintained version.

    https://s.olid.uk/id/BriJdHvXT2GMqgOaLgLwXg beta.11 ( does not throw )

    https://s.olid.uk/id/tRO_aXgvRdOqxu7ALzrgyw beta.10 ( throws )

  4. atk commented on May 13, 2026

    @atk
    ContributorAuthor

    My bad, it was an issue with pnpm. It is solved now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions