-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[feature](debug) support debug point used in debug code #24502
Conversation
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
TeamCity be ut coverage result: |
(From new machine)TeamCity pipeline, clickbench performance test result: |
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
(From new machine)TeamCity pipeline, clickbench performance test result: |
TeamCity be ut coverage result: |
4523ce3
to
e3369ba
Compare
run buildall |
1 similar comment
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
e3369ba
to
1895700
Compare
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
TeamCity be ut coverage result: |
(From new machine)TeamCity pipeline, clickbench performance test result: |
run buildall |
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.
clang-tidy made some suggestions
TeamCity be ut coverage result: |
(From new machine)TeamCity pipeline, clickbench performance test result: |
run buildall |
TeamCity be ut coverage result: |
(From new machine)TeamCity pipeline, clickbench performance test result: |
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.
clang-tidy made some suggestions
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.
clang-tidy made some suggestions
(From new machine)TeamCity pipeline, clickbench performance test result: |
run buildall |
run buildall |
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.
clang-tidy made some suggestions
run buildall |
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.
clang-tidy made some suggestions
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.
clang-tidy made some suggestions
TeamCity be ut coverage result: |
TeamCity be ut coverage result: |
TeamCity be ut coverage result: |
(From new machine)TeamCity pipeline, clickbench performance test result: |
(From new machine)TeamCity pipeline, clickbench performance test result: |
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.
LGTM
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
Proposed changes
Debug point is a code switch used for debug development.When a debug point is opened, the corresponding code can be executed.
Both fe and be support debug points.
For example, we want to debug publish version with TOO_MANY_VERSIONS error. Then we can add debug code in BE:
for fe, no macro DBUG_EXECUTE_IF, but just use function
DebugPointUtil.isEnable(debug_point)
to test if enable a debug point;To enable a debug point, we need two steps:
config.enable_debug_points = true
;/api/debug_point/add/{debug_point_name}
to the fe or be;Http API:
/api/debug_point/add/{debug_point_name}[?execute=times&timeout=seconds]
.execute
is optional, indicates the maximum number of times the debug point can take effect.timeout
is optional, indicates the maximum number of seconds the debug point takes effect;/api/debug_point/remove/{debug_point_name}
;/api/debug_point/clear
.Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...