-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
CT 1537 fix event test and rename a couple of fields #6293
Changes from all commits
b41b188
aeb3909
37a5d7c
075b97a
d1e2d03
7584c88
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -15,6 +15,7 @@ message EventInfo { | |
string thread = 7; | ||
google.protobuf.Timestamp ts = 8; | ||
map<string, string> extra = 9; | ||
string category = 10; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this eventually going to be the log category? Am I missing how this gets populated? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, right now it's just a placeholder. Eventually we'll populate it somehow... There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there an issue so we don't lose the fact we still need to actually populate it? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Mostly it's your ticket #5958. |
||
} | ||
|
||
// TimingInfo | ||
|
@@ -308,13 +309,13 @@ message ConnectionReused { | |
} | ||
|
||
// E007 | ||
message ConnectionLeftOpen { | ||
message ConnectionLeftOpenInCleanup { | ||
EventInfo info = 1; | ||
string conn_name = 2; | ||
} | ||
|
||
// E008 | ||
message ConnectionClosed { | ||
message ConnectionClosedInCleanup { | ||
EventInfo info = 1; | ||
string conn_name = 2; | ||
} | ||
|
@@ -327,13 +328,13 @@ message RollbackFailed { | |
} | ||
|
||
// E010 | ||
message ConnectionClosed2 { | ||
message ConnectionClosed { | ||
EventInfo info = 1; | ||
string conn_name = 2; | ||
} | ||
|
||
// E011 | ||
message ConnectionLeftOpen2 { | ||
message ConnectionLeftOpen { | ||
EventInfo info = 1; | ||
string conn_name = 2; | ||
} | ||
|
@@ -943,7 +944,7 @@ message NodeNotFoundOrDisabled { | |
} | ||
|
||
// I061 | ||
message GeneralMacroWarning { | ||
message JinjaLogWarning { | ||
EventInfo info = 1; | ||
string msg = 2; | ||
} | ||
|
@@ -1015,13 +1016,13 @@ message SelectorReportInvalidSelector { | |
} | ||
|
||
// M011 | ||
message MacroEventInfo { | ||
message JinjaLogInfo { | ||
EventInfo info = 1; | ||
string msg = 2; | ||
} | ||
|
||
// M012 | ||
message MacroEventDebug { | ||
message JinjaLogDebug { | ||
EventInfo info = 1; | ||
string msg = 2; | ||
} | ||
|
@@ -1227,11 +1228,12 @@ message LogSeedResult { | |
EventInfo info = 1; | ||
NodeInfo node_info = 2; | ||
string status = 3; | ||
int32 index = 4; | ||
int32 total = 5; | ||
float execution_time = 6; | ||
string schema = 7; | ||
string relation = 8; | ||
string result_message = 4; | ||
int32 index = 5; | ||
int32 total = 6; | ||
float execution_time = 7; | ||
string schema = 8; | ||
string relation = 9; | ||
} | ||
|
||
// Skipped Q017 | ||
|
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.
Along these same lines there's also a
GeneralMacroWarning
that is the catchall forwarn
defined inexceptions.py
. It's worth renaming that along with these.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.
It doesn't look like it's actually used anywhere. Can we just remove it?
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.
It's used within macros (docs)
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.
So it's exported into the context. So should we call it JinjaLogWarning?
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.
Or JinjaLogWarn?
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.
I went with JinjaLogWarning.