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

feat/mk1_support #1

Merged
merged 3 commits into from
Jan 6, 2025
Merged

feat/mk1_support #1

merged 3 commits into from
Jan 6, 2025

Conversation

builderjer
Copy link
Member

@builderjer builderjer commented Jan 6, 2025

Adds support for a Mark 1 device.

This does not setup the sound, just verifies that a Mark 1 is present.

Summary by CodeRabbit

  • New Features

    • Added device detection for Mark 1 hardware.
    • Implemented serial communication check for specific device identification.
  • Dependencies

    • Added pyserial library for serial communication support.
  • Improvements

    • Enhanced setup configuration to handle requirements file processing more flexibly.
    • Updated Python version in build tests to 3.10 for improved compatibility.

Copy link
Contributor

coderabbitai bot commented Jan 6, 2025

Warning

Rate limit exceeded

@builderjer has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 56 minutes and 27 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 6e5249f and 90ccac0.

📒 Files selected for processing (1)
  • .github/workflows/build_tests.yml (2 hunks)

Walkthrough

The pull request introduces a new function is_mark_1() in the ovos_i2c_detection module to detect the presence of a Mark 1 device through serial communication. A new pyserial dependency is added to support this functionality. Additionally, the setup.py file now includes a required() function that provides flexible handling of package requirements, allowing for loose version constraints when an environment variable is set. The GitHub Actions workflow has been updated to use Python version 3.10.

Changes

File Change Summary
ovos_i2c_detection/__init__.py Added is_mark_1() function to detect Mark 1 device via serial communication; imported serial and sleep
requirements.txt Added pyserial dependency
setup.py Introduced required() function for dynamic requirements processing
.github/workflows/build_tests.yml Updated Python version from 3.8 to 3.10 in the workflow configuration

Sequence Diagram

sequenceDiagram
    participant Device
    participant is_mark_1()
    participant Serial

    is_mark_1()->>Serial: Open /dev/serial0
    is_mark_1()->>Device: Send 'system.version'
    Device-->>is_mark_1(): Respond with "Command"
    is_mark_1()-->>is_mark_1(): Return True
Loading

Poem

🐰 A Rabbit's Ode to Device Detection

Serial signals dance through the wire,
Mark 1 whispers, a tech-driven choir
Pyserial magic, version checks so neat
Flexible requirements, a coding treat!
Detection complete, the rabbit cheers! 🎉


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (3)
ovos_i2c_detection/__init__.py (1)

3-3: Remove the unused sleep import.

The sleep function is never called, so retaining this import may lead to confusion.

-import subprocess
 import serial
-from time import sleep
🧰 Tools
🪛 Ruff (0.8.2)

3-3: time.sleep imported but unused

(F401)

setup.py (1)

35-43: Neatly handle environment variable logic in required() function.

The approach to replace strict version constraints with minimum version constraints when MYCROFT_LOOSE_REQUIREMENTS is set is a good practice to allow flexible dependencies in development/test environments. Consider adding a short docstring or comment explaining the purpose of this environment variable detection within the function, to improve maintainability.

requirements.txt (1)

1-1: Add a version specifier or flexible approach for pyserial.

While adding pyserial is necessary for serial communication, it’s often beneficial to set a minimum version (e.g., pyserial>=3.0) to ensure compatibility and security updates.

-pyserial
+pyserial>=3.0
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c6198a1 and 211ca1f.

📒 Files selected for processing (3)
  • ovos_i2c_detection/__init__.py (2 hunks)
  • requirements.txt (1 hunks)
  • setup.py (2 hunks)
🧰 Additional context used
🪛 Ruff (0.8.2)
ovos_i2c_detection/__init__.py

3-3: time.sleep imported but unused

(F401)


70-70: Do not use bare except

(E722)

Comment on lines +58 to +72
def is_mark_1():
if is_wm8960():
try:
ser = serial.Serial("/dev/serial0", 9600, timeout=3)
ser.write(b'system.version')
while True:
is_mk1 = ser.readline().decode().rstrip()
if is_mk1 and "Command" in is_mk1:
# This is a Mark 1
return True
break
return False
except:
return False

Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Avoid bare except and ensure the serial port is properly closed.

  1. Replace the bare except with a more specific exception (e.g., except serial.SerialException:).
  2. Consider ensuring the serial port is properly closed, for example by using a with serial.Serial(...) as ser: construct so that exceptions don’t leave the port left open.

Below is a sample diff showcasing more specific exception handling and a context manager for closing the serial connection:

-def is_mark_1():
-    if is_wm8960():
-        try:
-            ser = serial.Serial("/dev/serial0", 9600, timeout=3)
-            ser.write(b'system.version')
-            while True:
-                is_mk1 = ser.readline().decode().rstrip()
-                if is_mk1 and "Command" in is_mk1:
-                    # This is a Mark 1
-                    return True
-                break
-            return False
-        except:
-            return False
+def is_mark_1():
+    if is_wm8960():
+        try:
+            with serial.Serial("/dev/serial0", 9600, timeout=3) as ser:
+                ser.write(b'system.version')
+                while True:
+                    is_mk1 = ser.readline().decode().rstrip()
+                    if is_mk1 and "Command" in is_mk1:
+                        return True
+                    break
+            return False
+        except serial.SerialException:
+            return False
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
def is_mark_1():
if is_wm8960():
try:
ser = serial.Serial("/dev/serial0", 9600, timeout=3)
ser.write(b'system.version')
while True:
is_mk1 = ser.readline().decode().rstrip()
if is_mk1 and "Command" in is_mk1:
# This is a Mark 1
return True
break
return False
except:
return False
def is_mark_1():
if is_wm8960():
try:
with serial.Serial("/dev/serial0", 9600, timeout=3) as ser:
ser.write(b'system.version')
while True:
is_mk1 = ser.readline().decode().rstrip()
if is_mk1 and "Command" in is_mk1:
return True
break
return False
except serial.SerialException:
return False
🧰 Tools
🪛 Ruff (0.8.2)

70-70: Do not use bare except

(E722)

setup.py Outdated
Comment on lines 57 to 60
install_requires=required("requirements/requirements.txt"),
packages=['ovos_i2c_detection'],
) No newline at end of file
)
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Codebase verification

Requirements file path mismatch will cause installation failure

The requirements.txt file exists in the root directory, but setup.py is looking for it at requirements/requirements.txt. This mismatch will cause the installation to fail. Either:

  • Move the file to requirements/requirements.txt, or
  • Update setup.py to use requirements.txt instead of requirements/requirements.txt
🔗 Analysis chain

Confirm that requirements/requirements.txt is available.

Be sure that the file requirements/requirements.txt is present and correct in the repository structure before installing. Otherwise, this call could lead to an error if the file is missing.

Below is a script to check if the file is present in the repo:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Ensure the requirements file is in place.
fd 'requirements.txt'

Length of output: 38


Script:

#!/bin/bash
# Check for requirements.txt in the requirements directory and verify if root file is a symlink
fd -t f 'requirements.txt' -d 2
ls -la requirements.txt

Length of output: 137

@builderjer builderjer merged commit 9215fb8 into dev Jan 6, 2025
1 of 2 checks passed
@builderjer builderjer deleted the feat/mark1 branch January 6, 2025 13:36
@coderabbitai coderabbitai bot mentioned this pull request Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant