I found 20 node processes were running on my machine (some for weeks) all related to running local E2E tests — it looks like each project within a temp directory was still running yarn rw dev processes. My guess is that it's related to the "dirty shutdown" issue here:
This is not a v1 high-priority to resolve, but I want
Let's move the CI over to Github Actions!
from the entities page, when you navigate to an entity, the general setting tab is selected and you can see data,
but from the entity itself, when you want to navigate to a related entity, the related entity state is not set on the general settings tab.
I expect that the general setting tab would be selected while navigating from one e
In the example above I ran wasp db studio, and as you can see, at some point prisma studio, which is being run in the background, printed some stuff first to stdout and then stderr.
What Wasp does is append (stderr) in front of any stderr output, to make it clear it came from
We could improve the readability / experience reading through the library source code if there were module level docstrings.
All python modules should include a docstring explaining
Add a description, image, and links to the prisma topic page so that developers can more easily learn about it.
To associate your repository with the prisma topic, visit your repo's landing page and select "manage topics."
Bug description
On windows, I run
prisma formatand note the unusual file ending. The lines are all LF, but the very last line is CRLF.This causes issue on my Linux CI where it formats it ending in LF's only, causing a diff to occur and the build to fail.
How to reproduce
![image](https://user-images.g