-
Notifications
You must be signed in to change notification settings - Fork 5k
fix: join crash issue #34421
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: join crash issue #34421
Conversation
Summary of ChangesHello @dapan1121, 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 addresses a crash issue encountered during join operations by refining memory management within the query executor. It also introduces enhanced debugging configurations for join-related tests, which will aid in diagnosing and preventing similar issues in the future. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe 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
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 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. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request correctly fixes a use-after-free crash in dynqueryctrloperator.c by moving the destruction of pUidList to after its last use. The change is sound. The modification in the Python test file enables debug flags, which was likely helpful for debugging. I've added a suggestion to refactor the test configuration for better readability and maintainability.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This pull request fixes a crash issue in join queries by correcting a use-after-free bug and adding debug configuration to the join test suite.
Changes:
- Fixed use-after-free bug in
buildBatchExchangeOperatorParamwhere array was destroyed before being accessed in trace logging - Added debug flag configurations to join test class to enable detailed logging for debugging join-related issues
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| source/libs/executor/src/dynqueryctrloperator.c | Moved taosArrayDestroy call after trace logging to prevent use-after-free |
| test/cases/14-JoinQueries/test_join_full.py | Added debug configuration dictionaries to enable detailed logging for join tests |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Description
Issue(s)
Checklist
Please check the items in the checklist if applicable.