-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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
Change sharkiqpy to sharkiq #68864
Change sharkiqpy to sharkiq #68864
Conversation
Hey there @ajmarks, mind taking a look at this pull request as it has been labeled with an integration ( |
I agree that the pypi package should be updated due to @ajmarks unavailability since December of 2020. If possible, I also believe @JeffResc, your fork should have at least 1 or 2 write-access maintainers added to it on the off-chance that you disappear like @ajmarks did. (Hopefully not but things happen lol) |
That sounds like a good idea to me as well. If anyone is interest in maintaining the project in the event of my disappearance, please let me know. |
@JeffResc Looks like you have https://github.com/JeffResc/sharkiq/ setup to publish to |
@JeffResc I'd also be willing to be a maintainer if any are still needed. |
Yep, I used that same automation on a few other repos and it works flawlessly. @funkybunch @AritroSaha10 Added and added. |
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.
Since merging this PR would remove the stale sharkiq
repo I'd recommend also updating lines 890
and 891
in CODEOWNERS
to the maintainers of the new upstream repo: @JeffResc @funkybunch @AritroSaha10
.
CODEOWNERS
Outdated
/homeassistant/components/*/translations/ |
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.
The change here is unrelated - no need to add a trailing carriage return
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.
Should be all set 👍
This is all set as well now |
"codeowners": ["@ajmarks"], | ||
"iot_class": "cloud_polling", | ||
"loggers": ["sharkiq"] | ||
} |
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.
Since #68877 has been merged, please add a carriage return here, or it will fail
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.
This should be all set now
Translation files should not be adjusted manually. Line 4 in cb5c7dc
|
This reverts commit c2d99f2.
Oops, I did this manually as the pre-commit hooks inside my dev container don't seem to function properly, this should be fixed |
I see that the new package uses very strict dependencies: I am a bit worried that it might cause issues in the future, when bumping those in HomeAssistant:
|
I normally pin the exact version that it's tested on just to ensure that nothing changes between the development environment, testing environment, and production environment, but I see what you mean here. How do you feel about:
|
Sounds good |
Sorry - it looks like you have kept both sync and async methods available. I'm generally of the view that new packages shouldn't bother with a sync version but if you are happy to continue supporting both then that's fine. |
To add additional context, this upstream repo is a fork of the existing integration which is stale with the maintainer unresponsive (that repo uses synchronous methods via I think there are a few places we should refactor and I'm happy if you wanted to create an issue on the dependency's repo to move everything to asynchronous; but, the key part of this PR is to update the dependency to a repo that is actively maintained. For now the integration is broken because the API URL changed, but so far that is the only difference between the old stale repo and this new repo. |
Please rebase over latest dev to fix CI (due to #68900) |
This is all set
I think @funkybunch summed this up quite nicely, but there is already some discussion about this in the sharkiq repo. |
So what do I need to do to fix? Will the update push on it's own? |
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.
Lgtm
If your home assistant instance is pulling updates from the If you want to update it manually see the discussion in this issue: #68624 Just know that if you make these changes manually they will be overwritten if you update home assistant |
Proposed change
The SharkIQ integration is currently broken, see #68624.
This PR changes the underlying pypi package from sharkiqpy to sharkiq. The original maintainer of sharkiqpy seems unreachable, so I forked the repository and made the necessary changes to fix the SharkIQ vacuum integration.
Edit: If @ajmarks continues to be unavailable, I would be interested in maintaining this, as long as no one else wants to.
sharkiq Changelog
const.py
to reflect the newDEVICE_URL
andLOGIN_URL
to connect to the Shark API.Type of change
Additional information
Checklist
black --fast 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
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: