Skip to content

nax_pyunifi.controller not found#1108

Merged
jokob-sk merged 1 commit intonetalertx:mainfrom
scalerow:bugfix/unifimp_not_running
Jul 4, 2025
Merged

nax_pyunifi.controller not found#1108
jokob-sk merged 1 commit intonetalertx:mainfrom
scalerow:bugfix/unifimp_not_running

Conversation

@scalerow
Copy link
Contributor

@scalerow scalerow commented Jul 4, 2025 •
edited by coderabbitai bot
Loading

Could not import nax_pyunifi.controller, pyunifi.controller works as expected.

Error occured in docker environment.

If I'm missing something, that's fine, just close my PR.

Summary by CodeRabbit

  • Chores
    • Updated internal dependencies to improve compatibility.

@scalerow
nax_pyunifi.controller not found
c7d9ef9 
Could not import nax_pyunifi.controller, pyunifi.controller works as expected.
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 4, 2025 •
edited
Loading

Walkthrough

The import path for the Controller class in the Unifi import script was updated from nax_pyunifi.controller to pyunifi.controller. No other code or logic in the script was changed.

Changes

File(s) Change Summary
front/plugins/unifi_import/script.py Updated import path for Controller class.

Poem

In the land of code, a path did shift,
From "nax" to "py", a subtle lift.
The Controller hops to a new domain,
While logic and flow remain the same.
A gentle change, a tidy fix—
The rabbit smiles at code that clicks! 🐇✨

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 608fc5b and c7d9ef9.

📒 Files selected for processing (1)
  • front/plugins/unifi_import/script.py (1 hunks)
🔇 Additional comments (1)
front/plugins/unifi_import/script.py (1)

15-15: No remaining nax_pyunifi references – import path is correct

  • front/plugins/unifi_import/script.py now uses
    from pyunifi.controller import Controller
  • Ran rg -n nax_pyunifi across the repo; no occurrences found

All stale imports have been removed and the new path works as intended.

✨ Finishing Touches
  • 📝 Generate Docstrings
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@jokob-sk jokob-sk merged commit 6203c3c into netalertx:main Jul 4, 2025
2 checks passed
@jokob-sk
Copy link
Collaborator

jokob-sk commented Jul 4, 2025

Thanks @scalerow - left in some test code 🤦‍♂️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@scalerow @jokob-sk