fix: add missing closing brace in CMD_SET_DEVICE_TIME handler #47

Merged
okapteinis merged 1 commit from security/critical-fixes-5-vulns into nightly 2025-12-27 16:28:06 +02:00
okapteinis commented 2025-12-27 16:27:40 +02:00 (Migrated from github.com)

Syntax error fix - missing closing brace for timestamp validation else block. This caused build failure in CI/CD.

Error:
examples/simple_repeater/MyMesh.cpp:1489:5: error: expected '}' before 'else'

Fix: Added closing brace after settimeofday error handling (line 1488)

🤖 Generated with Claude Code

Description

Type of Change

  • Bug fix (non-breaking change fixing an issue)
  • New feature (non-breaking change adding functionality)
  • Breaking change (fix or feature causing existing functionality to change)
  • Documentation update
  • Hardware support addition
  • Performance improvement

Testing Performed

  • Builds successfully on affected platforms
  • Tested on physical hardware
  • Verified no new compiler warnings
  • Checked memory usage
  • Example applications still work
  • Documentation updated

Hardware Tested

  • Device:
  • Firmware variant:
  • Test results:

Code Quality Checklist

  • Follows existing code style
  • No dynamic memory allocation in inappropriate places
  • No reformatting of existing code
  • Added comments for non-obvious logic
  • Updated documentation
  • CHANGELOG.md updated if applicable

Breaking Changes

Screenshots/Logs

Additional Notes

Syntax error fix - missing closing brace for timestamp validation else block. This caused build failure in CI/CD. Error: examples/simple_repeater/MyMesh.cpp:1489:5: error: expected '}' before 'else' Fix: Added closing brace after settimeofday error handling (line 1488) 🤖 Generated with [Claude Code](https://claude.com/claude-code) ## Description <!-- Provide a clear description of what this PR does --> ## Type of Change <!-- Mark relevant items with [x] --> - [ ] Bug fix (non-breaking change fixing an issue) - [ ] New feature (non-breaking change adding functionality) - [ ] Breaking change (fix or feature causing existing functionality to change) - [ ] Documentation update - [ ] Hardware support addition - [ ] Performance improvement ## Related Issues <!-- Link related issues: Fixes #123, Relates to #456 --> ## Testing Performed <!-- Describe testing done --> - [ ] Builds successfully on affected platforms - [ ] Tested on physical hardware - [ ] Verified no new compiler warnings - [ ] Checked memory usage - [ ] Example applications still work - [ ] Documentation updated ## Hardware Tested <!-- List hardware tested, or write "N/A" if documentation-only --> - Device: - Firmware variant: - Test results: ## Code Quality Checklist - [ ] Follows existing code style - [ ] No dynamic memory allocation in inappropriate places - [ ] No reformatting of existing code - [ ] Added comments for non-obvious logic - [ ] Updated documentation - [ ] CHANGELOG.md updated if applicable ## Breaking Changes <!-- Describe any breaking changes and migration path, or write "None" --> ## Screenshots/Logs <!-- Add screenshots or serial logs if applicable --> ## Additional Notes <!-- Any additional information for reviewers -->
gemini-code-assist[bot] commented 2025-12-27 16:27:51 +02:00 (Migrated from github.com)

Summary of Changes

Hello @okapteinis, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a build-breaking syntax error in the MyMesh.cpp file, specifically within the CMD_SET_DEVICE_TIME handler. The absence of a closing brace was causing compilation failures in the CI/CD environment. By adding the missing brace, the PR ensures the project can build successfully and maintains the integrity of the codebase.

Highlights

  • Syntax Error Fix: A critical syntax error, specifically a missing closing brace, has been resolved in the CMD_SET_DEVICE_TIME handler.
  • Build Failure Resolution: This fix directly addresses a build failure that was occurring in the CI/CD pipeline due to the aforementioned syntax error.
  • Code Structure Correction: The change involves adding a single closing brace after the settimeofday error handling block in MyMesh.cpp, restoring correct code structure.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩︎

## Summary of Changes Hello @okapteinis, I'm Gemini Code Assist[^1]! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request resolves a build-breaking syntax error in the `MyMesh.cpp` file, specifically within the `CMD_SET_DEVICE_TIME` handler. The absence of a closing brace was causing compilation failures in the CI/CD environment. By adding the missing brace, the PR ensures the project can build successfully and maintains the integrity of the codebase. ### Highlights * **Syntax Error Fix**: A critical syntax error, specifically a missing closing brace, has been resolved in the `CMD_SET_DEVICE_TIME` handler. * **Build Failure Resolution**: This fix directly addresses a build failure that was occurring in the CI/CD pipeline due to the aforementioned syntax error. * **Code Structure Correction**: The change involves adding a single closing brace after the `settimeofday` error handling block in `MyMesh.cpp`, restoring correct code structure. <details> <summary><b>Using Gemini Code Assist</b></summary> <br> The full guide for Gemini Code Assist can be found on our [documentation page](https://developers.google.com/gemini-code-assist/docs/review-github-code), here are some quick tips. <b>Invoking Gemini</b> You can request assistance from Gemini at any point by creating a comment using either `/gemini <command>` or `@gemini-code-assist <command>`. Below is a summary of the supported commands on the current page. Feature | Command | Description --- | --- | --- Code Review | `/gemini review` | Performs a code review for the current pull request in its current state. Pull Request Summary | `/gemini summary` | Provides a summary of the current pull request in its current state. Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in pull request comments and review comments. Help | `/gemini help` | Displays a list of available commands. <b>Customization</b> To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a `.gemini/` folder in the base of the repository. Detailed instructions can be found [here](https://developers.google.com/gemini-code-assist/docs/customize-gemini-behavior-github). <b>Limitations & Feedback</b> Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up [here](https://google.qualtrics.com/jfe/form/SV_2cyuGuTWsEw84yG). <b>You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the [Gemini Code Assist IDE Extension](https://cloud.google.com/products/gemini/code-assist).</b> </details> [^1]: Review the [Privacy Notices](https://policies.google.com/privacy), [Generative AI Prohibited Use Policy](https://policies.google.com/terms/generative-ai/use-policy), [Terms of Service](https://policies.google.com/terms), and learn how to configure Gemini Code Assist in GitHub [here](https://developers.google.com/gemini-code-assist/docs/customize-gemini-behavior-github). Gemini can make mistakes, so double check it and [use code with caution](https://support.google.com/legal/answer/13505487).
gemini-code-assist[bot] (Migrated from github.com) reviewed 2025-12-27 16:29:32 +02:00
gemini-code-assist[bot] (Migrated from github.com) left a comment

Code Review

This pull request correctly fixes a syntax error in MyMesh.cpp by adding a missing closing brace in the CMD_SET_DEVICE_TIME command handler, which was causing a build failure. The fix is correct and necessary. While reviewing the fix, I noticed a small opportunity for future improvement in the same error handling block: the use of ERR_CODE_ILLEGAL_ARG for a settimeofday() failure could be revisited. Since the timestamp argument is validated before this call, a failure is more of an internal error. A more specific error code could be beneficial for client-side error handling. That said, this is outside the scope of the current fix, which is approved.

## Code Review This pull request correctly fixes a syntax error in `MyMesh.cpp` by adding a missing closing brace in the `CMD_SET_DEVICE_TIME` command handler, which was causing a build failure. The fix is correct and necessary. While reviewing the fix, I noticed a small opportunity for future improvement in the same error handling block: the use of `ERR_CODE_ILLEGAL_ARG` for a `settimeofday()` failure could be revisited. Since the timestamp argument is validated before this call, a failure is more of an internal error. A more specific error code could be beneficial for client-side error handling. That said, this is outside the scope of the current fix, which is approved.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ojars/MeshCore!47
No description provided.