-
Notifications
You must be signed in to change notification settings - Fork 4
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
TimeoutError: Worker process failed to connect #4
Comments
Hmm, this one isn't immediately obvious. Could you provide the full logs of the run? You can put them in a toggleable summary tag, as shown here https://gist.github.com/scmx/eca72d44afee0113ceb0349dd54a84a2 |
I can't seem to get that formatted to a code block. I've uploaded log files instead. |
Thanks for the logs! Could you try #5 to see if it fixes your issue? I can't replicate it locally. |
Still running into an error unfortunately.
|
Thanks for testing the fix, and for your patience. It seems like the worker process DOES run, but doesn't connect to the main process. I thought the 5s timeout mightn't be long enough on your system, but seems like that's not the issue. In #5 I've now:
Could you give it another shot? Hope this fix works, but if not, please share the worker logs in |
Hi, if you're looking inside the container check |
Found it, thanks. Here's one of the logs generated. |
Hey, thanks for the worker logs, and for your patience. I've got two potential fixes :P First one's on #5 – the guess here is that your PC is faster than mine, and therefore the subprocess wins the race condition against the reverse connection TCP socket server in the main process. It now ensure that the server starts before starting the worker process. If that doesn't work, second one is on a branch called Could you give it another try? Thanks for playtesting. EDIT: sorry, neglected to push the 2nd branch until right now |
I'm getting the following error.
After 3 retries, the frontend app shows the following error.
![image](https://private-user-images.githubusercontent.com/63192778/399873674-07431b0e-596c-483f-8871-a52a82960532.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNjY3NzIsIm5iZiI6MTczOTE2NjQ3MiwicGF0aCI6Ii82MzE5Mjc3OC8zOTk4NzM2NzQtMDc0MzFiMGUtNTk2Yy00ODNmLTg4NzEtYTUyYTgyOTYwNTMyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEwVDA1NDc1MlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWIzOWIwOWJjMTkzMDU3ZGEwNTU5N2EwNmFmZTIzYzU3NzBhMzY4OWQwNTA1MThhMzNiNzZmNGU3NDI1OGY5MTEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.WH4GSTFU4mILEG0RaU2thKZpvNK7wy6wMGKNIYuVLgQ)
The text was updated successfully, but these errors were encountered: