-
-
Notifications
You must be signed in to change notification settings - Fork 35.8k
sharkiq dependency bump to 1.4.2
#153931
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
sharkiq dependency bump to 1.4.2
#153931
Conversation
Fixing authentication for Europe by using Auth0 and using library version 1.4.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
|
Hey there @JeffResc, @funkybunch, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
|
@home-assistant rename |
sharkiq dependency bump to 1.4.1
| async with asyncio.timeout(API_TIMEOUT): | ||
| LOGGER.debug("Initialize connection to Ayla networks API") | ||
| await ayla_api.async_sign_in() | ||
| await ayla_api.async_sign_in(True) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Freebien forcing True here will force an authentication method that will break the integration for users outside of the EU. We may need another upstream dependency update to work around this.
Could you test out this PR locally and let me know if it works for you without any parameters in the ayla_api.async_sign_in() method?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just tested the PR and it works as intended !
This should be better indeed. I didn't thought it would break for outside the EU.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Freebien just cut a new release for the upstream library. If you remove this Boolean in both places and update your PR to 1.4.2 of the dependency then you can reopen the issue and I’ll approve.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or @joostlek are you saying that the expected behavior is for 2nd level dependencies to not show up in requirements_all.txt?
If that’s the case the I’ll submit approval and no further changes will be needed.
|
@home-assistant add-label needs-more-information |
|
Marking this as draft. Pease mark it as ready when the concerns raised are addressed. |
Rollback to before async_sign_in(True) to allow non EU users to authent
|
@home-assistant remove-label needs-more-information |
sharkiq dependency bump to 1.4.1sharkiq dependency bump to 1.4.2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Freebien!
Proposed change
Fixing authentication for Europe by using Auth0 and using library version 1.4.2.
Here is the release for the sharkiq library that has been updated : https://github.com/sharkiqlibs/sharkiq/releases/tag/v1.4.2
Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: