You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding unit tests, I found that the hashing algorithm in ScrapeConfigsHandler() for the target allocator results in the same hash if the only thing that has changed is a regex value. The regex struct used in prometheus has no exported fields, so the hashing algorithm creates the same hash for both scrape configs. This results in a false negative, and the old object returned in the http response.
When adding unit tests, I found that the hashing algorithm in ScrapeConfigsHandler() for the target allocator results in the same hash if the only thing that has changed is a regex value. The regex struct used in prometheus has no exported fields, so the hashing algorithm creates the same hash for both scrape configs. This results in a false negative, and the old object returned in the http response.
Unit test:
opentelemetry-operator/cmd/otel-allocator/server/server_test.go
Line 622 in 782b582
previous scrape configs:
new scrape configs:
The text was updated successfully, but these errors were encountered: