There is a problem how CQRlog logs QSOs that start prior to midnight GMT and end after midnight GMT.

If you start a QSO prior to midnight GMT (23:55 example) and end the QSO after midnight GMT (00:05 example) CQRlog will take log the entry as 23:55 with tomorrows date. Then for the next 24 hours all logged QSOs will be logged PRIOR to the example above.

How long has this been going on and no one has noticed?

This means the date will be tomorrow's date but will have a time of say 23:55.

I'm running CQRlog v2.5.2, fldigi v4.1.20 along with fldigi xmlrpc.

I currently have CQRlog setup to start fldigi as remote.

The problem I'm having is the way the mode gets logged. As an example. When operating the digital mode Olivia, it will log as Olivia-8/500 or Olivia-32-1k.
At the end of the day when I upload my new QSOs to eQSL and LoTW, I get errors telling me that the mode is invalid. I then have to go into each and every log entry and change the mode to a valid entry such as: Changed Olivia-8/500 to OLIVIA, changed THOR8 to THOR.

Hi Saku!
Possibly due to classing FT4 as mode MFSK, I notice that, per band, any previously logged FT4 stations calling CQ always appear in CQ-monitor in UPPER case. Normally they should be reported in lower case, as happens in all other modes. Not really a problem, but still a bit confusing!
Robin, 9H1ZZ

Raspberry Pi 4 running Bullseye 32-bit
Cqrlog Ver:2.5.1 (001) Date:2021-01-24

I have over 1000 entries in eQSL, the vast majority of them from before I started using CQRlog in mid-February 2022.

When I download with the starting date set as 2022-02-15, I can successfully download any new QSLs; but I also get an annoying error message claiming that I have QSOs that are not in my log. When I check the eQSL_error.txt, the entries are clearly not after my CQRlog start date. And oddly enough they are both from the same call, but over a year apart.

Any thoughts?

GA,
after upgrade Mysql under Mint 20.2 y have this this error:
2021-12-11T11:44:01.834659Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.27-0ubuntu0.20.04.1) starting as process 8354
2021-12-11T11:44:01.896763Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.