You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Listen only to stdout for test-proxy errors (#2897)
Resolves#2715. On Windows, listening on stderr was keeping the
test-proxy process alive and it wasn't shutting down after all tests
completed. There may be a better solution using PTY, but stock support
in std or okio for PTY isn't adequate in Windows and this narrow use
case doesn't currently warrant the amount of effort I put into
heaths/akv-cli-rs to fix a similar problem.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -207,6 +207,12 @@ Similarly, if running on the command line pass `PROXY_MANUAL_START=true`.
207
207
To log tracing information to the terminal, you can add the `RUST_LOG` environment variable as shown above using the [same format supported by `env_logger`](https://docs.rs/env_logger/latest/env_logger/#enabling-logging).
208
208
The targets are the crate names if you want to trace more or less for specific targets e.g., `RUST_LOG=info,azure_core=trace` to trace information messages by default but detailed traces for the `azure_core` crate.
209
209
210
+
To log traces from the [Test Proxy] itself, pass `test-proxy=trace` to `RUST_LOG` e.g.,
211
+
212
+
```sh
213
+
RUST_LOG=info,azure_core=debug,test-proxy=trace cargo test -p azure_security_keyvault_secrets --test secret_client
214
+
```
215
+
210
216
#### Debugging in Windows
211
217
212
218
Using the recommended [CodeLLDB] Visual Studio Code extension on Windows will stop at breakpoints but may not pretty print variables e.g.,
0 commit comments