Skip to content

Typo in log on update forward opcode mismatch

The OPCODE shown in the log message emitted when incoming opcode is unexpected in zone.c is wrong. The change in this MR should fix it. I believe it's almost self-explanatory. I actually first noticed it in forward_callback(), but while working on this report I've realized there are several similar cases. This MR should fix all of them.

Edited by Mark Andrews

Merge request reports