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

fix(zigbee): Add default destructor to Window Covering and fix initialization of tm struct #10943

Merged
merged 1 commit into from
Feb 6, 2025

Conversation

P-R-O-C-H-Y
Copy link
Member

Description of Change

This PR add a quick fix that adds a default empty destructor + fixing a warning of uninitialized members of tm structure in addTimeCluster(); method

Tests scenarios

Compiled without any errors and warnings

Related links

@P-R-O-C-H-Y P-R-O-C-H-Y self-assigned this Feb 6, 2025
@P-R-O-C-H-Y P-R-O-C-H-Y added the Area: Zigbee Issues and Feature Request about Zigbee label Feb 6, 2025
@P-R-O-C-H-Y P-R-O-C-H-Y requested a review from me-no-dev February 6, 2025 12:51
Copy link
Contributor

github-actions bot commented Feb 6, 2025

Messages
📖 🎉 Good Job! All checks are passing!

👋 Hello P-R-O-C-H-Y, we appreciate your contribution to this project!


📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

Click to see more instructions ...


This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 3655d54

Copy link
Contributor

github-actions bot commented Feb 6, 2025

Memory usage test (comparing PR against master branch)

The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.

MemoryFLASH [bytes]FLASH [%]RAM [bytes]RAM [%]
TargetDECINCDECINCDECINCDECINC
ESP32C6000.000.00000.000.00
ESP32H2000.000.00000.000.00
Click to expand the detailed deltas report [usage change in BYTES]
TargetESP32C6ESP32H2
ExampleFLASHRAMFLASHRAM
Zigbee/examples/Zigbee_CarbonDioxide_Sensor0000
Zigbee/examples/Zigbee_Color_Dimmable_Light0000
Zigbee/examples/Zigbee_Color_Dimmer_Switch0000
Zigbee/examples/Zigbee_Contact_Switch0000
Zigbee/examples/Zigbee_Dimmable_Light0000
Zigbee/examples/Zigbee_Occupancy_Sensor0000
Zigbee/examples/Zigbee_On_Off_Light0000
Zigbee/examples/Zigbee_On_Off_Switch0000
Zigbee/examples/Zigbee_Pressure_Flow_Sensor0000
Zigbee/examples/Zigbee_Scan_Networks0000
Zigbee/examples/Zigbee_Temp_Hum_Sensor_Sleepy0000
Zigbee/examples/Zigbee_Temperature_Sensor0000
Zigbee/examples/Zigbee_Thermostat0000
Zigbee/examples/Zigbee_Window_Covering0000

Copy link
Contributor

github-actions bot commented Feb 6, 2025

Test Results

 62 files   62 suites   5m 39s ⏱️
 21 tests  21 ✅ 0 💤 0 ❌
153 runs  153 ✅ 0 💤 0 ❌

Results for commit 3655d54.

@me-no-dev me-no-dev added the Status: Pending Merge Pull Request is ready to be merged label Feb 6, 2025
@me-no-dev me-no-dev merged commit 5ba4c21 into espressif:master Feb 6, 2025
74 of 79 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Zigbee Issues and Feature Request about Zigbee Status: Pending Merge Pull Request is ready to be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants