You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When updating probes, the connection status indicator alternates between the correct "Updating..." text, and another text like "Not updated" or "Updated (some time ago)". This is confusing for users, as they may think the update either failed or is done, when it in reality is still in progress (note: the status indicator doesn't affect the updating itself).
I'm pretty sure this is because of how the parsed log content is cached in a global variable in ansible.py (which is bad even if it is not the cause of the problem). A way to solve this may be to use Redis, but that's perhaps a little overkill. It's also possible to remove the caching, but this will lead to increased disk I/O (possibly with a factor around 5-10) and increased CPU usage (the file will need to be parsed each time).
The text was updated successfully, but these errors were encountered:
When updating probes, the connection status indicator alternates between the correct "Updating..." text, and another text like "Not updated" or "Updated (some time ago)". This is confusing for users, as they may think the update either failed or is done, when it in reality is still in progress (note: the status indicator doesn't affect the updating itself).
I'm pretty sure this is because of how the parsed log content is cached in a global variable in ansible.py (which is bad even if it is not the cause of the problem). A way to solve this may be to use Redis, but that's perhaps a little overkill. It's also possible to remove the caching, but this will lead to increased disk I/O (possibly with a factor around 5-10) and increased CPU usage (the file will need to be parsed each time).
The text was updated successfully, but these errors were encountered: