Skip to content
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

BUG: Regularly receiving 'Failed to connect to server' while working on build scripts #2805

Closed
davesmith00000 opened this issue Oct 1, 2023 · 2 comments · Fixed by #2879
Closed
Labels
bug The issue represents an bug
Milestone

Comments

@davesmith00000
Copy link
Contributor

Here's a screenshot, this happens every 4-5 builds, and I can recover by doing rm -fr out.

image

Running using millw, Mill 0.11.4, VSCode + Metals (latest snapshot)

What I'm doing is working on the Mill build scripts and generated classes. My suspicion is that the Metals build import - which also uses millw I just discovered - is competing with my command line builds and one is corrupting or crashing the other (perhaps restarting the build server? Just a guess).

Here is the repo where I was doing the work:

https://github.com/davesmith00000/shaders

@lefou
Copy link
Member

lefou commented Oct 2, 2023

Does your edit and generate process involve some manual removal of files in the out directory?

@davesmith00000
Copy link
Contributor Author

Only overwriting generated sources.

@lolgab lolgab added the bug The issue represents an bug label Oct 2, 2023
lolgab added a commit that referenced this issue Nov 16, 2023
Attempt to fix #2805
We now catch the exception, delete the content of the mill-worker-xyx
directory and try again.
Seems to be working correcly from manual tests
lolgab added a commit to lolgab/mill that referenced this issue Nov 16, 2023
Attempt to fix com-lihaoyi#2805
We now catch the exception, delete the content of the mill-worker-xyx
directory and try again.
Seems to be working correcly from manual tests
lolgab added a commit to lolgab/mill that referenced this issue Nov 16, 2023
Attempt to fix com-lihaoyi#2805
We now catch the exception, delete the content of the mill-worker-xyx
directory and try again.
Seems to be working correcly from manual tests
lolgab added a commit to lolgab/mill that referenced this issue Nov 16, 2023
Attempt to fix com-lihaoyi#2805
We now catch the exception, delete the content of the mill-worker-xyx
directory and try again.
Seems to be working correcly from manual tests
lolgab added a commit to lolgab/mill that referenced this issue Nov 16, 2023
Attempt to fix com-lihaoyi#2805
We now catch the exception, delete the content of the mill-worker-xyx
directory and try again.
Seems to be working correcly from manual tests
lolgab added a commit that referenced this issue Nov 16, 2023
Attempt to fix #2805 We now
catch the exception, delete the content of the mill-worker-xyx directory
and try again.
Seems to be working correcly from manual tests.

Pull request: #2879
@lefou lefou added this to the 0.11.6 milestone Nov 16, 2023
lolgab added a commit to lolgab/shaders that referenced this issue Nov 18, 2023
It should fix the issue reported at: com-lihaoyi/mill#2805
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue represents an bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants