[Bug] A division by zero exception is triggered when max_frame_size
in the node configuration file node.yaml is changed to 0
#14958
Labels
bug
Something isn't working
🐛 Bug
I changed the value of
validator_network.max_frame_size
in the node configuration file node.yaml. Specifically, I set it to 0, and after starting the node, a division by zero panic occurred during runtime.To reproduce
1.Change the value of
validator_network.max_frame_size
in the node configuration file node.yaml to 0.2. Restart the node to update the config.
3. A division by zero exception occurred when the node used the value of
max_frame_size
, causing the node to crash.Stack trace/error message
Here is the full log.
node.log
Below is part of the log.
Expected Behavior
Aptos is able to handle almost all misconfiguration issues and provides user-friendly relevant prompts. Therefore, I believe this division by zero exception should be handled to prevent the node from crashing unexpectedly.
System information
Please complete the following information:
The text was updated successfully, but these errors were encountered: