search

abhinavsingh / proxy.py

💫 Ngrok FRP Alternative • ⚡ Fast • 🪶 Lightweight • 0️⃣ Dependency • 🔌 Pluggable • 😈 TLS interception • 🔒 DNS-over-HTTPS • 🔥 Poor Man's VPN • ⏪ Reverse & ⏩ Forward • 👮🏿 "Proxy Server" framework • 🌐 "Web Server" framework • ➵ ➶ ➷ ➠ "PubSub" framework • 👷 "Work" acceptor & executor framework
https://abhinavsingh.com/proxy-py-a-lightweight-single-file-http-proxy-server-in-python/
BSD 3-Clause "New" or "Revised" License
3.01k stars 573 forks source link

Support --hostnames #1325

Closed alexey-pelykh closed 1 year ago

alexey-pelykh commented 1 year ago

@abhinavsingh your turn to tame your CI :)

abhinavsingh commented 1 year ago

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.

abhinavsingh commented 1 year ago

@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.

alexey-pelykh commented 1 year ago

@abhinavsingh how's it going on your end? any changes needed?

abhinavsingh commented 1 year ago

@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.

abhinavsingh commented 1 year ago

@alexey-pelykh LGTM, made few minor edits directly in the PR. Workflow revealed failures which led me to https://github.com/home-assistant/core/issues/91283 🤦‍♂️ Damn. Will need to fix the develop branch workflow before merging this PR