Skip to content
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

backfills tests for behaviour on malformed due to non-string tags #3695

Merged
merged 1 commit into from
Feb 8, 2024

Conversation

codefromthecrypt
Copy link
Member

@codefromthecrypt codefromthecrypt commented Jan 17, 2024

This adds tests to prove that all zipkin collectors return errors when json is malformed due to non-string tags.

See #3503 (comment)

@codefromthecrypt codefromthecrypt requested a review from reta January 17, 2024 16:07
@@ -222,7 +221,9 @@ public static <T> void writeList(WriteBuffer.Writer<T> writer, List<T> value, Wr

static IllegalArgumentException exceptionReading(String type, Exception e) {
String cause = e.getMessage() == null ? "Error" : e.getMessage();
if (cause.contains("Expected BEGIN_OBJECT") || cause.contains("malformed")) {
if (cause.contains("Expected BEGIN_OBJECT")
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

while this normalizes the error as intended, this PR already shows any data that has malformed tags in zipkin were created out-of-band, like not using zipkin, as all collectors regardless of HTTP or Kafka use this path

@codefromthecrypt codefromthecrypt changed the title WIP: backfill tests for behaviour on malformed due to non-string tags backfills tests for behaviour on malformed due to non-string tags Feb 7, 2024
@codefromthecrypt codefromthecrypt marked this pull request as ready for review February 7, 2024 16:03
@codefromthecrypt codefromthecrypt merged commit 66b152c into master Feb 8, 2024
12 checks passed
@codefromthecrypt codefromthecrypt deleted the backfill-tag-type-error branch February 8, 2024 02:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant