| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
…zy RPCs such as reads & writes * Fixes for WriteChannel * Fixes for RadChannel * Fixes for BlobWriteSession * Fixes for BlobReadSession `s$com.google.cloud.storage.Storage/readAs$com.google.cloud.storage.Storage/blobReadSession/readAs$g` * Fixes for BlobAppendableUpload
| public void setScope() { | ||
| if (scope != null) { | ||
| clearScope(); | ||
| } | ||
| scope = span.makeCurrent(); | ||
| } |
There was a problem hiding this comment.
This looks great! TIL to have explicit scope handling added to properly activate spans for lazy RPCs
Sorry, something went wrong.
Accidentally opened after some debugging in #3255
Accidentally opened after some debugging in #3255
…zy RPCs such as reads & writes The initial attempt at this could leak scope and result in new spans being nested incorrectly. This approach attempts to be less clever, but bounds all scopes so there isn't any leaking. Followup to #3255
| Back | FazBrowse Home | New Git URL |
Prior to these fixes the grpc/call/interceptCall could end up orphaned from the span that the RPC was actually performed for.
Now it looks like the following (The interceptCall is properly parented by the createFrom span):
