mod: update elastic/mito to version v1.15.0 #40294
Merged
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.
Proposed commit message
This brings error-handling improvements.
If elastic/mito#71 is merged before this PR closes, I think it would be worth adding that into this change and bumping to v1.15.0.Now included in this change.Note that runtime error handling is still not perfect.
I will come back to this later.I've looked into this and what I was thinking was happening is happening; the_+_
call is returning an error type and there is noget
overload for an error. It looks like the CEL runtime is not decorating/throwing when the_+_
call returns the error, so the next call is what gives error location annotation. There is not anything we can do about this at this level, and the error quality is reasonable. I may take another look at the runtime later.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs