8000 Nextbus self throttle by ViViDboarder · Pull Request #146064 · home-assistant/core · GitHub
[go: up one dir, main page]

Skip to content

Nextbus self throttle #146064

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

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

ViViDboarder
Copy link
Contributor

Proposed change

Used new client feature to keep track of rate limits and self throttle when approaching the threshold. This will result in less errors and hopefully make it less likely that they block our UA if we're acting responsibly.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

This should help avoid rate limit exceeded errors
@ViViDboarder ViViDboarder force-pushed the nextbus-self-throttle-full branch from 8cc64b0 to 022e087 Compare June 3, 2025 15:47
@ViViDboarder ViViDboarder marked this pull request as ready for review June 3, 2025 15:47
Comment on lines +37 to +38
self.client: NextBusClient = NextBusClient(agency_id=agency)
self._agency: str = agency
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
self.client: NextBusClient = NextBusClient(agency_id=agency)
self._agency: str = agency
self.client = NextBusClient(agency_id=agency)
self._agency = agency

types should be inferred here, no need for explicit typing

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using basedpyright, it gives me this warning:

Type annotation for attribute client is required because this class is not decorated with @final [reportUnannotatedClassAttribute]

The rule seems to be new in basedpyright because type checking misses changed types otherwise.

I don't think it's worth doing for it's own sake, but since I'm updating the module, might as well.

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.

Error Updating Data from API - NextBus
2 participants
0