Describe the bug
I have just detected an issue where Wing Commander is not correctly handling errors when connecting to the Discovery Server API to validate Node connectivity.
If the connection fails the last know result is used (ie a cached result). This is not ideal, but under normal conditions should not impact the function.
I will be addressing this issue ASAP and expect to push an update tonight for it (all going well).
To Reproduce
Steps to reproduce the behavior:
Run Wing Commander Bot
Ensure connection to Discovery Server is available. Check by browsing to the Discovery Server website http://discovery.skycoin.net:8001/#/
Issue the `/start' command to Wing Commander.
Issue the '/status' command to force a re-check of the Discovery Server
Prevent access to the Discovery Server (block it in your firewall or other method)
Issue the /status command again. An error should be logged to the command terminal (if your running in interactive mode, but no notification will be sent to Telegram session. The Bot will respond with the previous data - which makes everything look fine.
Expected behavior
The user should be informed that the Discovery Server was unable to be contacted and that the Bot was unable to verify connectivity of the Nodes with the Discovery server at this point in time.
Describe the bug I have just detected an issue where Wing Commander is not correctly handling errors when connecting to the Discovery Server API to validate Node connectivity.
If the connection fails the last know result is used (ie a cached result). This is not ideal, but under normal conditions should not impact the function.
I will be addressing this issue ASAP and expect to push an update tonight for it (all going well).
To Reproduce Steps to reproduce the behavior:
/status
command again. An error should be logged to the command terminal (if your running in interactive mode, but no notification will be sent to Telegram session. The Bot will respond with the previous data - which makes everything look fine.Expected behavior The user should be informed that the Discovery Server was unable to be contacted and that the Bot was unable to verify connectivity of the Nodes with the Discovery server at this point in time.