-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Cappl 1067 distinguish capability error types #20316
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
base: develop
Are you sure you want to change the base?
Conversation
|
I see you updated files related to
|
| // TODO whats the correct combination of events/metrics/logging and statuses for user errors? | ||
| c.lggr.Debugw("Capability execution succeeded with user error", "capID", request.Id, "capReqCallbackID", request.CallbackId, "userErr", err) | ||
| _ = events.EmitCapabilityFinishedEvent(ctx, loggerLabels, c.WorkflowExecutionID, request.Id, meteringRef, store.StatusCompleted, request.Method, err) | ||
| c.metrics.IncrementTotalWorkflowStepErrorsCounter(ctx) |
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 probably want to change this into a new metric specifically for user errors.
|
shouldn't you also change the server_request.go to handle old in favour of |
|




draft
Note, there are no changes required to the DON2DON shims in this version of the change which is the simple solution of prepending a string to the error to indicate its a user error (like is already done for remote reportable). Its possible that error metadata could be added to the response instead, however that will entail some change to the DON2DON shims (for example the response is not currently returned in the error case), so need to consider backwards compatability. Possibly a part 2, need to consider this some more.