-
Notifications
You must be signed in to change notification settings - Fork 180
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
V1.1.0 beta2 #421
V1.1.0 beta2 #421
Conversation
// TODO: This looks suspicious | ||
rsc.OriginConfig.DearticulateUpstreamRanges = true | ||
// // TODO: This looks suspicious | ||
// rsc.OriginConfig.DearticulateUpstreamRanges = true |
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.
?
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 believe this was put in for debugging purposes and forgotten about; so it is commented for Beta2 and will be scrubbed completely in the next release
// span := trace.SpanFromContext(pr.upstreamRequest.Context()) | ||
// _, span := tspan.NewChildSpan(pr.Context(), rsc.Tracer, "Fetch") | ||
// if span != nil { | ||
// pr.upstreamRequest = pr.upstreamRequest.WithContext(trace.ContextWithSpan(pr.upstreamRequest.Context(), span)) | ||
// defer span.End() | ||
// } | ||
|
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.
?
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.
this should be unneeded so as to minimize the span count, but I kept in comments in case it needs to come back, will be scrubbed in next release.
No description provided.