-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
googlecloudspannerreceiver: Update dependencies #36112
Comments
Pinging code owners for receiver/googlecloudspanner: @dashpole @dsimil @KiranmayiB @harishbohara11. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
One more update that needs addressing #36317 |
@dashpole there has been little traction on getting any of these issues looked at. I'm leaning towards removing this component once more |
Looking into it. |
Spanner dep was updated in #36685 |
…en-telemetry#37514) #### Description Supersedes open-telemetry#36202 #### Link to tracking issue Part of open-telemetry#36112
…37524) #### Description Supersedes open-telemetry#36209 Most of the changes are obvious renames or refactors. The non-obvious changes are: * `Start()` must now be called on the cache to enable cleanup in the background. * `Stop()` can only be called once (or it will block indefinitely). I've added a sync.Once to ensure it is only ever called once. * `Set()` and `Get()` no longer return errors--even if Stop has already been called. This makes some of our tests obsolete, and I removed those tests. #### Link to tracking issue Fixes open-telemetry#36112 --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Component(s)
receiver/googlecloudspanner
Describe the issue you're reporting
#30370 and #29830 were auto-closed since the previous codeowner didn't act on them. We should keep our dependencies up-to-date to ensure we stay on maintained versions of dependencies.
This issue is complete when:
The text was updated successfully, but these errors were encountered: