-
Notifications
You must be signed in to change notification settings - Fork 6
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
Feature/fix unmarshall error #110
base: ads-stage
Are you sure you want to change the base?
Conversation
Move Issuer Fetch Out of Loop
Experiment: Don't wait for processing to complete before committing the kafka offset
Append unmarshaling errors to the result set Instead of using hard coded constants, create an enum to contain various redemption statuses. This change does not remap the existing values and so does not require an ads-serve change.
Rather than using a new enum, use the enum generated by gogen-avro for status management. Also make log lines shorter by splitting across multiple lines.
return utils.ProcessingErrorFromErrorWithMessage(err, message, msg, logger) | ||
} | ||
|
||
err = Emit(producer, resultSetBuffer.Bytes(), logger) | ||
if err != nil { | ||
message := fmt.Sprintf("Request %s: Failed to emit results to topic %s", tokenRedeemRequestSet.Request_id, producer.Topic) | ||
message := fmt.Sprintf( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should increase Prometheus counters on these unexpected cases and wire alert manager to notify us.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
right before all return utils.ProcessingErrorFromErrorWithMessage(err, message, msg, logger)
instructions
No description provided.