Open atatadev opened 8 months ago
Thanks for reporting this. Is it possible to check if this happens on an example you can share? for example, take a sample project that uses same JDK, Gradle and framework/libraries that doesn't contain your company code/data, and see if it happens on that as well? This way we can try to reproduce it on our end in a better way.
Hey @atatadev , is this still happening to you?
The same issue happens here aswell with different gradle and java versions e.g OpenJDK 64-Bit Server VM Temurin-21.0.4+7 (build 21.0.4+7-LTS, mixed mode) + Gradle 8.6
The same issue happens here aswell with different gradle and java versions e.g OpenJDK 64-Bit Server VM Temurin-21.0.4+7 (build 21.0.4+7-LTS, mixed mode) + Gradle 8.6
Can you try adding this to your config please?
{
"feature": {
"network": {
"outgoing": {
"ignore_localhost": true
}
}
}
}
Bug Description
If I use mirrord cmd line with gradle, sometimes I face issue that it can’t communicate between its processes, examples:
./gradlew
gradle wrapper to execute task, which tries to communicate with daemon process, but can’t connectSteps to Reproduce
The issue is flaky and not always reproducible. But technically, it's just execute gradle tasks with mirrord
Backtrace
No response
Relevant Logs
Your operating system and version
Mac OS 14.3
Local process
gradlew (java)
Local process version
OpenJDK 64-Bit Server VM Zulu17.42+19-CA (build 17.0.7+7-LTS, mixed mode, sharing)
Additional Info
Config and logs: mirrord 3.92.1
mirrord.json agent-logs.txt gradle-daemon-connection-issue-log.txt gradle-fork-executor-issue-log.txt