Currently these emit a stack trace but don't mention the match/file in question. It would be much more useful if they did.
Something like 9d010b523216d5bb669930d0459c1fa6107d32b4 would be great. However that change hides the error information from the scorer, which relies on the current behaviour to show a useful error to the person editing the scores.
Fixing this therefore likely also involves creating a mechanism for the scorer to get all the errors, perhaps ideally with a way for it to know that it can discard the outer exception's message as that info is already available from context.
Currently these emit a stack trace but don't mention the match/file in question. It would be much more useful if they did.
Something like 9d010b523216d5bb669930d0459c1fa6107d32b4 would be great. However that change hides the error information from the scorer, which relies on the current behaviour to show a useful error to the person editing the scores.
Fixing this therefore likely also involves creating a mechanism for the scorer to get all the errors, perhaps ideally with a way for it to know that it can discard the outer exception's message as that info is already available from context.