Closed austinlparker closed 5 years ago
Please note - this is a breaking change on merge as it changes the default transport to proto over http.
What can we do about the breaking change?
Well, if someone's bringing in the package from NPM it's not a huge deal as minor bumps don't get automatically updated. I'm more concerned about people who may be using the dist
files directly from github as an ersatz CDN.
Quick update - I went ahead and did some manual testing since I'm pretty sensitive to the transport change... Passed in a context through extract that resulted in this -
SpanContextImp {
_baggage: {},
_guid: 'ffffffffffffffff',
_traceGUID: 'ffffffffffffffff' }
And was able to create a new span as a child of that context, then successfully serialized them to LightStep via protos -
So, I'm reasonably confident that we're not going to break anything with the proto change.
What's the behavior when it's empty access token and there's no local satellite running? Is there any helpful debug messages?
The satellite doesn't support sending an error message like that yet, so you'll get some generic response error from the transport.
FYI - this is also blocked on LS-7832.
Maybe a useful high verbosity info message? "INFO: You are running with an empty access token. This is only supported for Developer Mode reporting." or something?
sure, i like both of those ideas, i'll add them in.
sure, i like both of those ideas, i'll add them in.
TY, it LGTM on a cursory review