-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[refactor] - return privatekey verification errors #3164
base: main
Are you sure you want to change the base?
Conversation
Why both |
I didn't want to change the existing behavior where the error appears in the result. However, we still need the error returned from FromData. Otherwise, the only place to identify these errors would be in the results. This issue should be visible during the scan as early as possible. Additionally, if errors occur only on non-verified results and the scan is run with |
I see. It seems like a big code smell to have two different ways of aggregating errors, and the intention behind the code isn't clear. It would be clearer to use the same method throughout. e.g., having for err := range errChan {
allErrs = errors.Join(allErrs, err)
resultErrs = errors.Join(resultErrs, err)
} |
Description:
This PR logs any errors encountered during private key verification, ensuring the errors are both available in the result and recorded in the engine.
Checklist:
make test-community
)?make lint
this requires golangci-lint)?