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
Currently the automatic codegen feature works by invoking Gradle in continuous mode. While this was a handy way to implement this without having to replicate the file monitoring handled by Gradle, it has the disadvantage of keeping a daemon running always, in BUSY status (not available for other builds) - which consumes memory on the system.
Consider reverting to manually trigger the codegen task when GQL files are touched.
The text was updated successfully, but these errors were encountered:
Currently the automatic codegen feature works by invoking Gradle in continuous mode. While this was a handy way to implement this without having to replicate the file monitoring handled by Gradle, it has the disadvantage of keeping a daemon running always, in
BUSY
status (not available for other builds) - which consumes memory on the system.Consider reverting to manually trigger the codegen task when GQL files are touched.
The text was updated successfully, but these errors were encountered: