ham-radio-software
Conversion error in settings/msg_flush data
For the current "0.4.1.dev8-g536233c" Messages and Chat tabs I see: "06/21/2023 13:21:38:INFO:DratsConfig:Error in config file: settings/msg_flush data 30.000000 is not an int" pop up repeatedly in my MSYS2 MINGW64 shell status window. I don't seem to be able to use Preferences>Messages>Queue flush interval to correct it. The settings menu shows just "30". This issue does not appear to impact any Message or chat Chat function that I can tell. It appears to be an issue of the declared type for the value.
To submit a new issue, Click on the "NEW ISSUE" button.
Adding comments for a problem unrelated to exiting issue or Pull Request messes up tracking of issues.
It will also cause incorrect search results when people are searching for answers when they see similar problems.
This problem is that the it the configuration file has data stored in the wrong format, in this case floating format, where d-rats is attempting to read it as an integer.
The config parsing code for python3 does not auto convert input data as liberally as the python2 version did, and the python2 code had a bug where it was suppressing coding errors. The python3 version of d-rats is now throwing exceptions on all these cases so that we can find and fix them.
Assignment added and removed so that the original poster of the issue will be included in the update to the ticket.
The message is harmless, and will be removed at a later date.
In the past d-rats was silently ignoring many programming errors, and I have modified d-rats to to log those errors so that they can be fully investigated.
The issue here will take some major work in understanding and propably refactoring the config.py system.
The config dialog is storing these numbers that must be integers as string representation of floating point numbers. Then when the something reads in a something that must be a integer, the API throws an exception.
The proper fix is to store the number as the string representation of an integer. Another issue is that the Config UI allows manually entering a floating point number when it should not.