Saku and others,
I have been working on adding auto uploads for QRZ to the latest Alpha branch.
I think I have it solved. Here is a video of it in action under testing on my Arch system machine. I am not a developer or coder at all. I recently discovered Claude AI and used it to create the code to add the feature to the Alpha.141 fork. I also uploaded it to my github page if anyone wants to test it.
QRZ subscription is required for the auto upload to work from what I understand. Api Key from QRZ is required. I have both.
It seems to be working here. IF you try it please do so at your own risk. back up everything or use it in a USB stick version of Linux or a virtual box. etc.
IF it is good could this be added to the Alpha versions moving forward? I like having this additional feature.
Thoughts? Feedback? Bugs?
https://github.com/n8mus/cqrlog/tree/master
73
Jon N8EM formerly N8MUS
Doing more testing of the online upload of all logs in CQRLOG including my newly added QRZ upload feature.
I am observing in the status upload box that it repeats the prior call and then moves to the new one. This was observed in FT8 mode.
I did a video of the test available here: https://youtu.be/yz9kLh2fm7c
Everything seemed to upload perfectly. I am just unsure if there is an issue and why the status window is repeating stuff that has already been uploaded.
More work to do or leave it as it?
More testing.
73
Jon
Jon
HI Jon!
Interesting.
Did you test 141 before doing your QRZ extension?
How did it act then with Clublog? Is there same action with deleting the previous qso and then uploading it and the new one before doing any code changes?
I have not tested the Clublog part with FT8 so if there is an underlying bug it can reflect also to code you have added.
I have not yet looked at your code. I must download it next and see what changes there are.
--
Saku
OH1KH
Uhh!
Tried to find out the changes by looking at commits. But it seems to be very hard to pick up what have changed.
Looks like everything is changed. I think this is what you get with AI.
IMHO changes are needed just for few files in src folder, less than 10, roughly. Now it seems everything has been changed.
I think commit efef94c should hold all the needed changes.
How ever there are 819 files changed, with +1055001 lines changed what makes it impossible to track.
The database modifications should not be done manually by user. (Commit b76f6a3)
At Cqrlog start there is a check of database version number and with that it should trigger modification routine that does the job and increases database version number after successful update so that it does not happen another time.
If possible the database changes should be done so that it is backward compatible in case user reverts back to run older version for some reason.
I do not get the idea of Commit e1660bc, lnet lib. It looks (without doing diff) very same than already existing lnet lib.
This will need a lot of cleanup if it will be pull requested to CqrlogAlpha.
--
Saku
OH1KH