You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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>)
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
Prisma schema (if relevant):
The text was updated successfully, but these errors were encountered:
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:
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?
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.
prisma -v
ornpx prisma -v
):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
Prisma schema (if relevant):
The text was updated successfully, but these errors were encountered: