-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
Previously, all `Closer`s would use their own context (either captured in `Init` or derived from the one in `Init`) in the implementation of `Close` (for example, when they wanted to log something). However, due to the way the draining of the wrapped row-by-row processors and closing of `Closer`s is structured (the draining happens first), it was possible for the captured context to have a tracing span which was already `Finish`ed. This is so because the row-by-row processors derive separate tracing spans and finish them automatically during draining whereas the closure of `Closer`s happens later. This commit fixes this issue by passing a context as an argument to `Close` function, and most of the implementations now use that. Only components that derive their own tracing span are allowed to use their own context since they control when the span is finished. Release note: None
- Loading branch information
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.