subproject("io")
        subproject("stdlib-java-extensions")
        subproject("launcher")
        subproject("logging")
        subproject("logging-api")
        subproject("messaging")
        subproject("native")
        subproject("process-services")
        subproject("serialization")
        subproject("service-provider")
        subproject("time")
        subproject("tooling-api-provider")

        //if it's really dead we should deregister it if it is not already deregistered.
        //if the daemon is not dead we might continue receiving from it (and try to find the bug in messaging infrastructure)
        LOGGER.error("The message received from the daemon indicates that the daemon has disappeared."
            + "\nBuild request sent: {}"

            moduleRegistry.getModule("gradle-logging-api").getImplementationClasspath().getAsURLs(),
            moduleRegistry.getModule("gradle-messaging").getImplementationClasspath().getAsURLs(),
            moduleRegistry.getModule("gradle-files").getImplementationClasspath().getAsURLs(),

For example, issues may occur if a `{javaApi}/java/lang/SecurityManager.html[SecurityManager]` is modified in a test because
Gradle's internal messaging depends on reflection and socket communication, which may be disrupted if the permissions on the security manager change. In this particular case, you should restore the original `SecurityManager` after the test so that the

Class <org.gradle.process.internal.worker.messaging.WorkerConfig> is not annotated (directly or via its package) with @org.gradle.api.NonNullApi in (WorkerConfig.java:0)
Class <org.gradle.process.internal.worker.messaging.WorkerConfigSerializer> is not annotated (directly or via its package) with @org.gradle.api.NonNullApi in (WorkerConfigSerializer.java:0)