-
Notifications
You must be signed in to change notification settings - Fork 5
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
fix: broker forces connection closure #89
Comments
Hmmm, I can't reproduce this error. The same EDIT: Wrong logs uploaded. See comment below for real logs. |
I don't think it is causing any errors or none that I can see (services fire up without errors) and same errors are in your docker compose logs. Maybe its part of the process to force closure, idk. Saw it while looking at #88 so thought I should open an issue. If it matters which I don't think does, but here are my versions
|
Oops, I had uploaded your logs 😆 Mine don't have these errors (trying again): And my Docker versions are almost exactly the same (I have Can you post the output of |
Here are my prowes containers, I spun up after destroying everything just to be sure.
And yes I am using the latest commit on dev branch, below is output (
docker-compose-logs-dev-25f0.txt PS: containers aren't stopping, see below
|
Really strange... If I interpret these errors correctly, the connection to the workers drop. So if you were to send a workflow run request, it would likely not be processed. Can you confirm that? If, instead, everything works as expected, I guess I will close that issue for now. |
I am closing this, by above if you meant |
I meant the |
oh yeah 🤦♂️, I check my
and I seem to get an error,
I thought that this might be my system issue or something that I am facing due to my configs or something. I spun up a VM and tried to do the same there. Even though there are less
These are responses for host and VM respectively, I don't understand why it was happening so I thought may should have it documented. 👍 |
Describe the bug
While looking at
docker compose logs
I notice below error throughout.To Reproduce
Steps to reproduce the behavior:
Additional context
Below is my compose log.
dev.txt
The text was updated successfully, but these errors were encountered: