fix: Update latency check to use CLAIMED status#680
Open
evanh wants to merge 2 commits into
Open
Conversation
There was a chance that the latency metric would be very spiky if a message was moving between the PENDING and CLAIMED status. Update the check to use both statuses so the latency stays consistent.
markstory
reviewed
Jun 5, 2026
| activations[2].status = ActivationStatus::Claimed; | ||
| activations[2].received_at = now - Duration::from_secs(50); | ||
| assert!(store.store(activations).await.is_ok()); | ||
|
|
Member
There was a problem hiding this comment.
Should there also be a test for the claimed task having the highest latency?
| max_delayed_task_allowed_sec: 3600, | ||
| max_message_size: 5000000, | ||
| grpc_max_message_size: 10 * 1024 * 1024, // 10MB | ||
| grpc_max_message_size: 12 * 1024 * 1024, // 12MB |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a chance that the latency metric would be very spiky if a message was moving between the PENDING and CLAIMED status. Update the check to use both statuses so the latency stays consistent.