Closed lexx-bright closed 1 year ago
In our evironment we don't use this symbols, and no tests for them. Need to be fixed, release will be canceled.
@lexx-bright Can you test against current master ? All tests (unit and e2e) added and unescape work as expected. But additional check before release is not bad.
Carbon-clickhouse seems to be fixed. Raised a related issue https://github.com/go-graphite/graphite-clickhouse/issues/207 for graphite-clickhouse.
Also have a look at the building package actions, it says build successful, but if you look at the details of step "Push packages to the stable repo" it says it could not upload package as it already existed. Which makes sense, new package name should be carbon-clickhouse-0.11.3-2.x86_64.rpm
Yes, some changes in release cycle is needed. But may be before next release, now simple increment version.
This seems not to be fixed completely, as now tag values with spaces in them are stored with a +
. This breaks existing graphite queries and conflicts with tags where value actually have a +
sign.
Made new issue for that: #124
After 5257f8e6ec977b5fc3d777f9044061d2e87d8b00, Tag1 and Tags fields are uploaded unescaped. @msaf1980 stated this was intentional https://github.com/go-graphite/carbon-clickhouse/blob/1a337757495e47cfeef1f72dac362386273cb1b3/uploader/tagged.go#L85 But this change breaks queries using special symbols.