lightstep-tracer-python

lightstep-tracer-python copied to clipboard

Recently our Python-based project upgraded a lot of our dependencies, including lightstep, protobuf, and grpcio. Since then when we run our unit tests, we see several warning messages from lightstep...

EdLeafe

Fixed the examples argument parser problem of not handling booleans

3

Modified the argument parser for the --use_tls argument because it wasn't parsing booleans correctly.

andrewcheelightstep

Transport selection should be mutually exclusive

2

Setting thrift as the default value will fail because we check for http transport first (the default) - this should be changed so that either transport is mutually exclusive.

austinlparker

Client should handle system clock changes better

2

This should fix #77

wiedi

We're currently seeing our services spend a large amount of time inside of the lightstep sdk serializing reports when they instrument themselves with tracing. This is in large part due...

rowillia

Lightstep appears to be using pure python thrift code

3

I believe the issue is that https://github.com/lightstep/lightstep-tracer-python/blob/master/lightstep/crouton/ttypes.py was generated with 0.9.2, but lightstep now requires 0.10.0. Accessing the accelerated module appears to have changed since 0.10.0 (https://github.com/apache/thrift/pull/844). I recommend you...

rowillia

Protobufs are always owned by their parent. Constructing the children first and then passing it to the parent results in a large copy. https://developers.google.com/protocol-buffers/docs/reference/python-generated#repeated-message-fields

rowillia

isaaczinda

We have implemented a conformance test which validates a tracer's inject/extract carrier format. There is a conformance harness that sends a set of carriers to a client (written in python...

bg451

cartersocha