Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Log not updated after day change when resending messages #341

Closed
rsngt opened this issue Oct 24, 2023 · 4 comments
Closed

[BUG] Log not updated after day change when resending messages #341

rsngt opened this issue Oct 24, 2023 · 4 comments

Comments

@rsngt
Copy link

rsngt commented Oct 24, 2023

What OS and Version?

Windows 10,
8.5.2

Description of issue

I am sending a message repeatedly with the resend function (every 15 minutes). The log in the UI is updated with each new message sent, until midnight, when no new messages are displayed in the log. The messages are being sent, it's just that the log doesn't refresh in the UI. If I clear the log in the UI then the subsequent messages are shown in the log (until the next midnight).

This has been an issue for the last few versions.

@dannagle
Copy link
Owner

This is an amusing bug. I found the problem, and I know the fix.

The log table rolls over to "00:00:00" at midnight. The new packets actually are getting logged. They are getting sent to the bottom out of view. Over the course of 2 days, the logger will become a jumbled mess.

The proper fix is to include the full date so the sort will stay correct. Including the full date has been requested before (such as in #314), so I will try to have that in the next release. That will fix this problem too.

@Secure-Mobility
Copy link

This is an amusing bug. I found the problem, and I know the fix.

The log table rolls over to "00:00:00" at midnight. The new packets actually are getting logged. They are getting sent to the bottom out of view. Over the course of 2 days, the logger will become a jumbled mess.

The proper fix is to include the full date so the sort will stay correct. Including the full date has been requested before (such as in #314), so I will try to have that in the next release. That will fix this problem too.

Great, that's good news. I look forward to the updated release :-)

@dannagle
Copy link
Owner

This fix is now in the latest release. Closing.

@rsngt
Copy link
Author

rsngt commented Dec 22, 2023

This fix is now in the latest release. Closing.

Thanks Dan, I have downloaded and installed the update and can see the full timestamps in the log. I'll check again tomorrow once we cross midnight, but I'm sure this will fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants