-
-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mill fail to connect to the server with apple silicon M1 #1098
Comments
Hey @parzival3 what is "interactive version"? |
|
Various fixes only shown on Windows, probably also elsewhere. * Fixed string stream writer/reader used for mill client-server communication, by using an explicit charset for byte conversion * Avoid `java.nio.file.Paths.get(url.getFile())` in favour of `java.nio.file.Paths.get(url.toURI())` as the latter handles windows paths with leading drive letters well * Improved CI setup for Windows * Better run/spawn of Java sub-processes by selecting the same Java executable which is used by mill We still have some CI failures on Windows, as we need some of these fixed in mill before we can benefit from it. Expect more PRs. Probably related issues: * #781 * #874 * #646 * #1098 Commits: * CI: Added test on Windows * Try a better handing of windows absolute paths I hope to avoid a error like: Illegal char <:> at index 2: /D:/a/mill/mill/ * Improve string assertion message? * More details in assertion error * Use explicit charset for string-byte conversion * Search java exe in same JAVA_HOME as mill is using * CI: job deps * check for Win * Debug run java process Pull request: #1146
I've committed a potential fix for this (#1729), which is currently in release process. Until it's available, you can try the already mentioned |
Once Mill 0.10.1 is out, no explicit |
Step to reproduce the problem
and then
If I use the interactive version everything works 😃
The text was updated successfully, but these errors were encountered: