Bulk Clublog upload *serious* BUG

6 posts / 0 new
Last post
g8tmv
Bulk Clublog upload *serious* BUG

cqrlog is attempting to use the 'realtime' single QSO upload method to do bulk uploads to Clublog.
This is explicitly banned by Clublog because it causes too much traffic.

An example:

I enter a contest and make 140 QSOs. As I make each QSO it is uploaded to Clublog - this is okay.

After the contest I upload the QSOs to LotW - this causes the QSOs in cqrlog to be marked as updated.

Next time cqrlog does a Clublog upload (either because a new QSO happens or because the menu item to do a Clublog update is used) Each updated QSO is deleted and re-uploaded to Clublog using the realtime interface. After about 25 QSOs this causes Clublog to give an "Access Denied" message and lock the user out for about 1 hour.

See the Clublog Help info at:

https://clublog.freshdesk.com/support/solutions/articles/3000023706-exce...

https://clublog.freshdesk.com/support/solutions/articles/54905-how-to-up...

https://clublog.freshdesk.com/support/solutions/articles/3000110752-ip-a...

73 Colin G8TMV

oh1kh
Bulk Clublog upload *serious* BUG

Hi Colin!

Online logs are not my favorites. I do not use any and so have no way to test.
If I understood right making LoTW upload to qsos already sent to online logs causes reupload to online log.

May I ask have you tested this?

--
Saku
OH1KH

g8tmv
Testing Ignore changes for uploads to LotW

I have not tried it yet. But I will do.

*However* In the case of Clublog I actually need to upload the changes so that Clublog knows that the QSO's have been uploaded to LotW so that it can take account of this when suggesting QSL status.

g8tmv
Another update

1) The Ignore changes must happen at the time of the edit. It doesn't affect already marked QSOs so setting it did NOT stop the upload attempt of already edited QSOs when I tested it.

2) This is NOT a coding bug. It is a DESIGN bug. I suspect that Michael, G7VJR (the author of Clublog) added bulk uploads when the realtime uploads became a load problem (probably after Petr stopped development).

3) Misusing the realtime upload to do bulk uploads gets the user denied access after approx 40 uploads.

4) The links in my original bug report contain the information on how to do bulk uploads the correct way. Using the correct bulk method whenever the user uses the "Clublog -> Upload all changes" menu item will fix the problem.

If you can fix this I can test it for you, just send me a link to the new cqr6.zip (QT6)

73 Colin

oh1kh
Another update

1) Yep!
Change is "recorded" in table and only new qsos after ignore is set will be valid. For this "qsoList/online log/remove all upload triggers" will clean up the table.
But all tables! If more than one online log is used.

2) I do agree that the design is weird. And very hard to follow from source.

3) Then it might be better to disable auto upload. After all qsos are done make LoTW upload and after that do manual triggered upload to online log. I do not know does it any help as it might record the upload changes table same way as when auto upload is used.

4)I Have been trying to avoid touching the online log side. Just because it is a big mess that is not needed because THE log is Cqrlog itself.

--
Saku
OH1KH

g8tmv
More info

1) I did not know about the remove - that might help until it's fixed properly.

2) The problem is that it currently uses the "realtime upload" method for all uploads.
What it needs is some new code that uses the "bulk upload" method when you use the "Clublog -> Upload all changes" menu item.

3) I need auto upload working for my normal use. The problem occurs after I do a mass change to QSOs for example a LotW upload or if I do an adif import.

4) btw, Clublog is not actually a logging system. It is a system to help the user to get QSLs that are needed for awards or competitions. It is used as an extra system on top of a logging
program.

One thing which might work as a temporary fix is to put a time delay in the loop that does the bulk uploads to clublog. Maybe start with a 1 second delay between uploads and increase the delay by 1 second for every 5 transfers. It happens in the background so it shouldn't affect the user.

Also it might be worth asking Petr if he can take a look and fix it as it's rather urgent because users are getting "Access Denied" errors after about 40 QSO uploads.

73 Colin