opentelemetry-collector-contrib
opentelemetry-collector-contrib copied to clipboard
[exporter/loadbalancingexporter] ensure ring is properly initialized to prevent panic
Description: <Describe what has changed.> Ensure hashRing is not nil on start
Link to tracking Issue: <Issue number if applicable> https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/10110
Testing: Unit test added.
Documentation: No documentation change needed.
The committers listed above are authorized under a signed CLA.
- :white_check_mark: login: jvilhuber / name: Jan Vilhuber (4ad21c1f377177e33aa4ea857e302ba06a639956, 225f903cb5eaa5e95638b076b47ba980664efaae, 5af9d02eebe11ba04b100cf8c5bd7890e422e084, 0b09837518a6f571dd3d945395c0c8e854fc938a, 602fbad7b90eb0dbcb7895d7ba444fd8813841d2)
Thanks for the contribution @jvilhuber Can you sign the CLA as per community guidelines?
Thanks for the contribution @jvilhuber Can you sign the CLA as per community guidelines?
Yea I'm working on it with the company I work for at the moment. I assume it'll take some time. Sorry about that.
As discussed on Slack, the issue is related to initialisation of the component rather than nil slice, @jvilhuber is going to work on the fix and either update this branch/PR or create a separate one
This PR was marked stale due to lack of activity. It will be closed in 14 days.
Closed as inactive. Feel free to reopen if this PR is still being worked on.
What's the state of this PR? Do you need a code review?
What's the state of this PR? Do you need a code review?
I think mostly it's waiting on me (or rather my company) to sign the CLA (I'm still pushing; it's not controversial, just a matter of getting it done). More code-reviews can't hurt, though.
CLA authorization is still failing.
This PR was marked stale due to lack of activity. It will be closed in 14 days.
@jvilhuber, do you have any news on getting the CLA approved?
@jvilhuber, do you have any news on getting the CLA approved?
I keep pinging legal. Still waiting. Sorry.