[ui] Reject throttleLatest promise with a string instead of an Error #26452
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.
Summary & Motivation
When
throttleLatest
rejects the Promise for an active call, use a string instead of anError
to avoid surfacing unnecessary errors in our error tracking. Since the Promise rejection represents the function behaving as intended, theError
doesn't need to be tracked or raise any alarms.How I Tested These Changes
Repro the Promise rejection case by viewing a Job dag that has surfaced it. Verify that an error appears in the console. Verify that with this change, no error is surfaced.