Error in Studio from v0.0.116 to v0.0.117
See original GitHub issueEver since migrating from prisma2@0.0.1xx
to prisma2@0.0.117
and higher, I’m encountering the following error (use a new sqlite db for development each time). It’s still working for prisma2@0.0.116
so whatever happened between 0.0.116
and 0.0.117
broke something.
prisma2 lift save && prisma2 lift save && prisma2 dev
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Releases · termux/termux-app - GitHub
Termux - a terminal emulator application for Android OS extendible by variety of packages. - Releases · termux/termux-app.
Read more >Compiler/TMS320F28377D: #pragma DATASECTION ...
I have got it to compile without error by changing following things in the linker file. Increased the size of RAMGS3 from 0x01000...
Read more >Support | Download | AVerMedia
Fix update FW error problem ... 2 New Widget for VTube Studio. ... Version: AVerMedia CamEngine v0.0.0.6 (Chromebook)v0.0.0.6. OS: ChromeOS
Read more >ROBLOX API Differences - Anaminus
This page lists the differences between versions of the ROBLOX Lua API. September 26, 2018 ( 0.355.0.241665 → 0.356.0.242723 ). Added Property ImageButton....
Read more >Debian -- Source Packages in "bullseye"
... globus-gram-job-manager-callout-error (4.2-1) ... golang-gopkg-vmihailenco-msgpack.v2 (4.3.1-2); golang-gopkg-warnings.v0 (0.1.2-1.1) ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey @heymartinadams @nickreynke @Megoos, sorry for the delay in this response. We’ve been making some significant changes to Studio over the last few weeks, and I believe this error should be gone now. Could you guys try updating
prisma2
to the latest preview (preview-3) and try again?If you still see it, please let me know and I’ll look into it!
Yes, it is working fine in preview 3