-
Notifications
You must be signed in to change notification settings - Fork 17
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
Enhance verbose output of conformance client and enable stream conformance tests #212
Conversation
if (intVal == null || intVal < 1 || intVal > 5) { | ||
throw RuntimeException("value for $arg option should be an integer between 1 and 5; instead got '$v'") | ||
} | ||
verbosity = intVal |
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'd be in favor of just having -v <value>
/-v
(not -vv
) or just -v <value>
for simplicity.
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.
done
inetSocketAddress: InetSocketAddress, | ||
proxy: Proxy, | ||
protocol: Protocol?, | ||
ioe: IOException, |
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.
Does it make sense to print the exception stack trace too?
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.
The reason I didn't is because it wasn't really useful. These errors propagate to the caller, which means these exceptions already get logged elsewhere at just verbosity 1 or 2.
43a9fa2
to
b32f62a
Compare
c8e4b1c
to
7fad0d7
Compare
…ing okhttp event logger and logging decorator for http client
…w/ config instead of known-failing
7fad0d7
to
e416c20
Compare
…f 499) in tracing
This adds verbose output features to the conformance client. There are now 5 levels of verbosity --
-v
,-vv
, and-vvv
can be used to turn on the first three;-v 4
and-v 5
can be used to turn on the heavier trace output.I used this output, along with a newly added
--trace
flag to the conformance test runner, to troubleshoot the streaming failures. (This PR, #210, and #211 represent all of the changes made to get everything to work.)The levels of verbosity are:
send
. (These could be expected errors, for tests of error conditions, which is why they are not enabled at verbosity 1).HTTPClientInterface
implementation, to print out each step in an RPC.HTTPClientInterface
tracing, so that each step shows its full stack trace (useful since some operations can happen from different threads).This PR also applies some clean-up to the conformance configs and ... 🥁 ... enables all of the conformance tests! They now should all pass.