Skip to content

Conversation

Dhiren-codity
Copy link

Description

Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.

Fixes #(issue_no)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Documentation update

Checklist:

  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation.
  • My changes generate no new warnings.
  • I have added tests/screenshots (if any) that prove my fix is effective or that my feature works.
  • I have tested the tests implicated (if any) by my own code and they pass (make test or ctest -VV -R <test-name>).
  • If my change is significant or breaking, I have passed all tests with ./docker-compose.sh test &> output and attached the output.
  • I have tested my code with OPTION_BUILD_ADDRESS_SANITIZER or ./docker-compose.sh test-address-sanitizer &> output and OPTION_TEST_MEMORYCHECK.
  • I have tested my code with OPTION_BUILD_THREAD_SANITIZER or ./docker-compose.sh test-thread-sanitizer &> output.
  • I have tested with Helgrind in case my code works with threading.
  • I have run make clang-format in order to format my code and my code follows the style guidelines.

If you are unclear about any of the above checks, have a look at our documentation here.

Signed-off-by: Dhiren Mhatre <[email protected]>
@codity-dev
Copy link

codity-dev bot commented Oct 1, 2025

🔍 PR review started! Estimated time: 20-25 minutes.

💡 Learn More

Ask Codity questions:
Mention @codity {your question} in a comment to get answers about the code.

Trigger a manual review:
Comment @codity review on a PR or MR.

View Full Docs

@codity-dev
Copy link

codity-dev bot commented Oct 1, 2025

🔍 PR review is completed!

@Dhiren-codity
Copy link
Author

@codity review

@codity-dev
Copy link

codity-dev bot commented Oct 1, 2025

🔍 PR review started! Estimated time: 20-25 minutes.

💡 Learn More

Ask Codity questions:
Mention @codity {your question} in a comment to get answers about the code.

Trigger a manual review:
Comment @codity review on a PR or MR.

View Full Docs

@Dhiren-codity
Copy link
Author

@codity review

@codity-dev
Copy link

codity-dev bot commented Oct 1, 2025

🕐 A review is already in progress for this PR. Please wait until it completes before triggering another.

@codity-dev
Copy link

codity-dev bot commented Oct 1, 2025

🔍 PR review is completed!

@Dhiren-codity
Copy link
Author

@codity review

@codity-dev
Copy link

codity-dev bot commented Oct 1, 2025

🔍 PR review started! Estimated time: 20-25 minutes.

💡 Learn More

Ask Codity questions:
Mention @codity {your question} in a comment to get answers about the code.

Trigger a manual review:
Comment @codity review on a PR or MR.

View Full Docs

@codity-dev
Copy link

codity-dev bot commented Oct 1, 2025

🔍 PR review is completed!

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