By default tinyformat errors such as ‘wrong number of conversion specifiers in format string’ cause an assertion failure.
Raise an exception instead so that error handling can recover or can show an appropriate error.
By default tinyformat errors such as ‘wrong number of conversion specifiers in format string’ cause an assertion failure.
Raise an exception instead so that error handling can recover or can show an appropriate error.
By default tinyformat errors such as 'wrong number of conversion
specifiers in format string' cause an assertion failure.
Raise an exception instead so that error handling can recover or can
show an appropriate error.
It’s a matter of robustness. Let’s think about the following (completely imaginary) scenario:
Some rarely-hit debug logging code in the network code is using the wrong formatting. An attacker that can manage to hit this can bring down the entire node.
If we just raise a runtime exception, all it does is log and exception and kill the current connection. A nuisance instead of a DoS.