-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
fix: protocol check in B6 devices #320
fix: protocol check in B6 devices #320
Conversation
Important Review skippedAuto reviews are limited to specific labels. 🏷️ Labels to auto review (6)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #320 +/- ##
==========================================
- Coverage 39.89% 39.89% -0.01%
==========================================
Files 84 84
Lines 7607 7608 +1
==========================================
Hits 3035 3035
- Misses 4572 4573 +1 ☔ View full report in Codecov by Sentry. |
Why change it without an issue related? |
This is the only device with a check and IMHO was based on a "device" logic not a message one |
We shouldn't change it without any related issues. We might create issues and we need stability. |
Anyway we need to find a proper way to handle. If we don't change the logic, we need to introduce a constant for message protocol value(s) |
Or just skip that line. |
Nope, we will have doubts in future |
a9602a5
to
580ca0f
Compare
🤖 I have created a release *beep* *boop* --- ## [6.0.1](v6.0.0...v6.0.1) (2024-10-06) ### Bug Fixes * add missing body_type "163" ([#317](#317)) ([45f7bd2](45f7bd2)) * message protocol version default ([#316](#316)) ([2f4e5d1](2f4e5d1)) * protocol check in B6 devices ([#320](#320)) ([55659c1](55659c1)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
No description provided.