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
// TODO: We currently can't use `config::ENV_METRICS_FLUSH_INTERVAL_SECS`// because we need to be able to set the flush interval to a fraction of a// second. We should change config::ENV_METRICS_FLUSH_INTERVAL_SECS so that// it can support this.
This issue is about addressing that TODO. I suggest we implement #27 and then set the flush interval to whatever number of milliseconds is needed in the test harness.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
…S. (linkerd#28)
* Add initial tests for client and server connection handling w.r.t. TLS.
Add a simple framework for TLS connection handling and some initial tests
that use it.
An explicit effort has been made to keep the test configuration as close to the
production configuration as possible; e.g. we use regular TCP sockets instead of some
mock TCP sockets. This matters less now, but will matter more later, if/when we
implement more low-level TLS-over-TCP optimizations.
Rename `ConnectionConfig::identity` to `ConnectionConfig::server_identity` to make
it clearer that it is always the identity of the server, regardless of which role
the `ConnectionConfig` is being used in.
Signed-off-by: Brian Smith <brian@briansmith.org>
In proxy/tests/support/proxy.rs we have:
This issue is about addressing that TODO. I suggest we implement #27 and then set the flush interval to whatever number of milliseconds is needed in the test harness.
The text was updated successfully, but these errors were encountered: