Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't access Prisma Studio after changing filters and refreshing page #920

Closed
bhajneet opened this issue Apr 22, 2022 · 4 comments
Closed

Comments

@bhajneet
Copy link

  1. Prisma version (prisma -v or npx prisma -v):
prisma                  : 3.12.0
@prisma/client          : 3.12.0
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine 22b822189f46ef0dc5c5b503368d1bee01213980 (at node_modules/@prisma/engines/libquery_engine-darwin-arm64.dylib.node)
Migration Engine        : migration-engine-cli 22b822189f46ef0dc5c5b503368d1bee01213980 (at node_modules/@prisma/engines/migration-engine-darwin-arm64)
Introspection Engine    : introspection-core 22b822189f46ef0dc5c5b503368d1bee01213980 (at node_modules/@prisma/engines/introspection-engine-darwin-arm64)
Format Binary           : prisma-fmt 22b822189f46ef0dc5c5b503368d1bee01213980 (at node_modules/@prisma/engines/prisma-fmt-darwin-arm64)
Default Engines Hash    : 22b822189f46ef0dc5c5b503368d1bee01213980
Studio                  : 0.459.0
  1. Logs from Developer Tools Console or Command line, if any:
Invalid string length
RangeError: Invalid string length
    at JSON.stringify (<anonymous>)
    at _t.serialize (http://localhost:5555/assets/index.js:1:49091)
    at _t.update (http://localhost:5555/assets/index.js:1:12197)
    at Cc (http://localhost:5555/assets/vendor.js:50:6994)
    at _t.n (http://localhost:5555/assets/vendor.js:50:6688)
    at _t.update (http://localhost:5555/assets/index.js:1:48948)
    at Cc (http://localhost:5555/assets/vendor.js:50:6994)
    at _t.n (http://localhost:5555/assets/vendor.js:50:6688)
    at http://localhost:5555/assets/index.js:1:82151
    at Array.forEach (<anonymous>)
  1. Does the issue persist even after updating to the latest prisma CLI dev version? (npm i -D prisma@dev)
    No. Same error in 3.13.0-dev.29

  2. Prisma schema (if relevant):


@bhajneet
Copy link
Author

This has to do with the filters cached in browser. I can fix the issue by using incognito/private browsing or by clearing cache. However, it would be ideal to do this with a button press in the error message shown here:

image

Basically have prisma studio close all of its tabs and reset all its filters with some button press here. Neither "Reopen Studio" nor "Discard all unsaved changes" does this for me currently. I have to manually delete the site data to get it to work.

To do that, I inspect site with Chrome Dev Tools, go to the Application tab, then under Storage I tap "Clear site data" to get back in.

Is there a way for user to resolve this with a GUI click in the message shown in the picture above?

@shadoath
Copy link

shadoath commented Apr 22, 2022

I also have this issue, @bhajneet thank you for the clue about clearing the cache. Once I did this in Chome I could work with it again. Before I cleared it there was 400mb of storage, that seems like a LOT to me.
Screen Shot 2022-04-22 at 10 34 17

Looks to be related to #905 and possibly #917

@janpio
Copy link
Contributor

janpio commented Apr 22, 2022

See #895

@janpio
Copy link
Contributor

janpio commented Apr 22, 2022

Is this reproducible for you @bhajneet when you use the filters again? Can you get it into the same situation again?

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

No branches or pull requests

3 participants