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

Use proper signals #18613

Merged
merged 6 commits into from
Nov 21, 2018
Merged

Use proper signals #18613

merged 6 commits into from
Nov 21, 2018

Conversation

balloob
Copy link
Member

@balloob balloob commented Nov 21, 2018

Description:

We finally were using the aiohttp signals correctly since 3.4.4, we can move the work around now.

We were also using a deprecated way of running a HTTP server in emulated Hue.

Checklist:

  • The code change is tested and works locally.
  • Local tests pass with tox. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.

If the code does not interact with devices:

  • Tests have been added to verify that the new code works.

Co-Authored-By: balloob <paulus@home-assistant.io>
@balloob
Copy link
Member Author

balloob commented Nov 21, 2018

For the IP ban, the proper solution would be for it to be migrated to the storage helper.

@balloob
Copy link
Member Author

balloob commented Nov 21, 2018

I also realized that auth being a middleware means it's also being run for static resource requests 🤷‍♂️ I guess in a perfect world NGINX would sit in front of the static endpoint and serve that.

@balloob balloob merged commit 1341ecd into dev Nov 21, 2018
@ghost ghost removed the in progress label Nov 21, 2018
@balloob balloob deleted the use-proper-signals branch November 21, 2018 19:55
balloob added a commit that referenced this pull request Nov 29, 2018
* Emulated Hue not use deprecated handler

* Remove no longer needed workaround

* Add middleware directly

* Dont always load the ban config file

* Update homeassistant/components/http/ban.py

Co-Authored-By: balloob <paulus@home-assistant.io>

* Update __init__.py
@balloob balloob mentioned this pull request Nov 29, 2018
@balloob balloob added this to the 0.83.1 milestone Dec 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants