Support --hostnames #1325
Support --hostnames #1325
Conversation
alexey-pelykh
force-pushed
the
feature/multiple-hostnames
branch
4 times, most recently
from
1a4613b to
f5e3add
Compare
alexey-pelykh
force-pushed
the
feature/multiple-hostnames
branch
2 times, most recently
from
461a979 to
8341ea0
Compare
psf-chronographer
bot
added
the
bot:chronographer:provided
alexey-pelykh
force-pushed
the
feature/multiple-hostnames
branch
from
8341ea0 to
cb7921f
Compare
alexey-pelykh
force-pushed
the
feature/multiple-hostnames
branch
9 times, most recently
from
bc78ffc to
0942dba
Compare
alexey-pelykh
force-pushed
the
feature/multiple-hostnames
branch
from
4d58af2 to
467cb2e
Compare
|
@abhinavsingh your turn to tame your CI :) |
|
I restarted the failed jobs. Due to certain integration tests, which uses upstream httpbin.org and pythonhosted.org, we end up receiving server side / rate limiting errors. As a result, these tests can fail sometimes. Usually, restarting them always makes them work. |
|
@alexey-pelykh So workflow went fine after restarting failed jobs. Docker and GHCR are related to secrets and permissions for PRs I suppose. I'll take another stab at it sometime tonight or morrow and merge it. Thank you for adding this capability. It certainly can be used to scale proxy.py even further on a single host machine. |
|
@abhinavsingh how's it going on your end? any changes needed? |
Hi @alexey-pelykh , apologies, I got derailed a release work past/this week. Promise, I'll take a look again and merge this weekend. Thank you. |
|
@alexey-pelykh LGTM, made few minor edits directly in the PR. Workflow revealed failures which led me to home-assistant/core#91283 🤦♂️ Damn. Will need to fix the |
No description provided.