Menu
▾
▴
trustedqsl-testing
|
From: Rick M. <k1...@ar...> - 2023-09-12 00:29:13
|
I've been putting off release of 2.7 but there's now enough changes to push this over the wall. 2.7beta2 has several improvements; - The uploads database is updated from Oracle' Berkeley DB because the Oracle database is simply unusable, repeatedly corrupting the database for no reason. Since Oracle's database is fragile and breaks a lot, I've replaced the uploads database with SQLite. Hopefully this will eliminate the frequent database corruption. - Fixes for 1x1 callsign handling to stop validating against the FCC ULS database when an end-date is provided. - Allow OPERATOR in ADIF files to be longer than a normal callsign. If the OPERATOR is incorrectly set to the name of the operator, then it's not a callsign and will be ignored. - Update portable callsign handling. This now allows prefix/call like MU/K1MU and handles it properly. - Add a preference to allow callsigns in ADIF files to be ignored when signing. - Fix portable call handling for non-US stations "P5ROMEO/W4" used to require a US base call. - Restore the uploaded QSO database from the last backup when it gets corrupted. The other major change here is to build a "flatpak" image for Linux distributions. This allows install on most 64-bit Linux systems with no compiling needed. I just installed the latest Flatpak build on a Chromebook and a Raspberry Pi - easy peasy, Mac 64-bit builds now work on Apple Silicon (M1/M2 currently) systems. Mac 32-bit builds work on PPC and Intel i386. (Is anyone actually using the 32-bit Mac builds?) Kits: Windows: https://www.rickmurphy.net/lotw/tqsl-2.7.msi Mac, 64-bit: https://www.rickmurphy.net/tqsl-2.7.pkg Mac, 32-bit: https://www.rickmuphy.net/tqsl/tqsl-legacy-2.7.pkg Unix source: https://www.rickmurphy.net/tqsl/tqsl-2.7.tar.gz Linux Flatpak: https://flathub.org/apps/org.arrl.trustedqsl I'm very interested in upload testing due to the uploads database changes, and feedback on the Flatpak builds for Linux as that took a lot of work to get accepted in their repository. 73, -Rick -- Rick Murphy, D.Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA |
|
From: Richard S. <hob...@gm...> - 2023-09-12 02:26:22
|
I built a test package for Fedora and was able to upload my WSJT-X contacts. I noticed that usually I just upload everything and let it remove the duplicates for me. In this case it did not ask. Is that expected? Thanks, Richard KF5OIM |
|
From: Rick M. <k1m...@gm...> - 2023-09-12 03:18:05
|
The first time you run v2.7 it's going to discard the uploaded QSO history.
If you have an automatic backup enabled (File/Display or Modify
Preferences) and a good backup exists, then that data should be restored.
Is that consistent, or is there something else going on that I need to
investigate?
73,
-Rick
On Mon, Sep 11, 2023 at 10:29 PM Richard Shaw <hob...@gm...> wrote:
> I built a test package for Fedora and was able to upload my WSJT-X
> contacts.
>
> I noticed that usually I just upload everything and let it remove the
> duplicates for me. In this case it did not ask. Is that expected?
>
> Thanks,
> Richard
> KF5OIM
> _______________________________________________
> Trustedqsl-testing mailing list
> Tru...@li...
> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>
--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA
|
|
From: Richard S. <hob...@gm...> - 2023-09-12 11:44:30
|
On Mon, Sep 11, 2023 at 10:18 PM Rick Murphy <k1m...@gm...> wrote: > The first time you run v2.7 it's going to discard the uploaded QSO history. > If you have an automatic backup enabled (File/Display or Modify > Preferences) and a good backup exists, then that data should be restored. > Is that consistent, or is there something else going on that I need to > investigate? > Maybe I didn't explain it very quickly. Just as a test of the new version I did the usual first option in TQSL, sign and upload. On one of the pop-ups it asks for a date range to include which I never use. Once I click OK previously it would tell me I have XXX number of duplicates and XXX new contacts but this did not happen. Logging into the site I don't see duplicates or anything I just didn't know if it automatically skipped duplicates or re-processed all of my contacts. Thanks, Richard KF5OIM |
|
From: Richard S. <hob...@gm...> - 2023-09-12 11:45:01
|
On Tue, Sep 12, 2023 at 6:44 AM Richard Shaw <hob...@gm...> wrote: > On Mon, Sep 11, 2023 at 10:18 PM Rick Murphy <k1m...@gm...> > wrote: > >> The first time you run v2.7 it's going to discard the uploaded QSO >> history. >> If you have an automatic backup enabled (File/Display or Modify >> Preferences) and a good backup exists, then that data should be restored. >> Is that consistent, or is there something else going on that I need to >> investigate? >> > > Maybe I didn't explain it very quickly. Just as a test of the new version > I did the usual first option in TQSL, sign and upload. > correctly... Sorry still working on coffee #1 this morning. > > On one of the pop-ups it asks for a date range to include which I never > use. Once I click OK previously it would tell me I have XXX number of > duplicates and XXX new contacts but this did not happen. > > Logging into the site I don't see duplicates or anything I just didn't > know if it automatically skipped duplicates or re-processed all of my > contacts. > > Thanks, > Richard > KF5OIM > |
|
From: Rick M. <k1m...@gm...> - 2023-09-12 12:33:36
|
Thanks. I'll have a look.
73,
-Rick
On Tue, Sep 12, 2023 at 7:45 AM Richard Shaw <hob...@gm...> wrote:
> On Tue, Sep 12, 2023 at 6:44 AM Richard Shaw <hob...@gm...> wrote:
>
>> On Mon, Sep 11, 2023 at 10:18 PM Rick Murphy <k1m...@gm...>
>> wrote:
>>
>>> The first time you run v2.7 it's going to discard the uploaded QSO
>>> history.
>>> If you have an automatic backup enabled (File/Display or Modify
>>> Preferences) and a good backup exists, then that data should be restored.
>>> Is that consistent, or is there something else going on that I need to
>>> investigate?
>>>
>>
>> Maybe I didn't explain it very quickly. Just as a test of the new version
>> I did the usual first option in TQSL, sign and upload.
>>
>
> correctly... Sorry still working on coffee #1 this morning.
>
>>
>> On one of the pop-ups it asks for a date range to include which I never
>> use. Once I click OK previously it would tell me I have XXX number of
>> duplicates and XXX new contacts but this did not happen.
>>
>> Logging into the site I don't see duplicates or anything I just didn't
>> know if it automatically skipped duplicates or re-processed all of my
>> contacts.
>>
>> Thanks,
>> Richard
>> KF5OIM
>>
> _______________________________________________
> Trustedqsl-testing mailing list
> Tru...@li...
> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>
--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA
|
|
From: Rick M. <k1m...@gm...> - 2023-09-12 19:15:24
|
I've just tried this and got the expected "This log contains x QSO(s) which
appear to have already been signed for upload to LoTW.." dialog.
73,
-Rick
On Tue, Sep 12, 2023 at 8:33 AM Rick Murphy <k1m...@gm...> wrote:
> Thanks. I'll have a look.
> 73,
> -Rick
>
> On Tue, Sep 12, 2023 at 7:45 AM Richard Shaw <hob...@gm...> wrote:
>
>> On Tue, Sep 12, 2023 at 6:44 AM Richard Shaw <hob...@gm...>
>> wrote:
>>
>>> On Mon, Sep 11, 2023 at 10:18 PM Rick Murphy <k1m...@gm...>
>>> wrote:
>>>
>>>> The first time you run v2.7 it's going to discard the uploaded QSO
>>>> history.
>>>> If you have an automatic backup enabled (File/Display or Modify
>>>> Preferences) and a good backup exists, then that data should be restored.
>>>> Is that consistent, or is there something else going on that I need to
>>>> investigate?
>>>>
>>>
>>> Maybe I didn't explain it very quickly. Just as a test of the new
>>> version I did the usual first option in TQSL, sign and upload.
>>>
>>
>> correctly... Sorry still working on coffee #1 this morning.
>>
>>>
>>> On one of the pop-ups it asks for a date range to include which I never
>>> use. Once I click OK previously it would tell me I have XXX number of
>>> duplicates and XXX new contacts but this did not happen.
>>>
>>> Logging into the site I don't see duplicates or anything I just didn't
>>> know if it automatically skipped duplicates or re-processed all of my
>>> contacts.
>>>
>>> Thanks,
>>> Richard
>>> KF5OIM
>>>
>> _______________________________________________
>> Trustedqsl-testing mailing list
>> Tru...@li...
>> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>>
>
>
> --
> Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA
>
--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA
|
|
From: Richard S. <hob...@gm...> - 2023-09-17 12:27:46
|
On Tue, Sep 12, 2023 at 2:15 PM Rick Murphy <k1m...@gm...> wrote: > I've just tried this and got the expected "This log contains x QSO(s) > which appear to have already been signed for upload to LoTW.." dialog. > 73 > Interesting, I tried a second time and for me it was the same as the first, no prompt... Thanks, Richard KF5OIM |
|
From: Rick M. <k1m...@gm...> - 2023-09-17 13:10:16
|
I'd have a look at your upload logs on Logbook - are you seeing previously
uploaded QSOs showing up?
Note that this practice - upload everything and let the software filter the
new ones - is strongly discouraged.
The upload data kept by TQSL is per-computer so QSOs uploaded from one
computer won't be recorded on any others (unless you backup the first and
restore the TBK to the others.)
What platform are you using?
73,
-Rick
On Sun, Sep 17, 2023 at 8:31 AM Richard Shaw <hob...@gm...> wrote:
> On Tue, Sep 12, 2023 at 2:15 PM Rick Murphy <k1m...@gm...> wrote:
>
>> I've just tried this and got the expected "This log contains x QSO(s)
>> which appear to have already been signed for upload to LoTW.." dialog.
>> 73
>>
>
> Interesting, I tried a second time and for me it was the same as the
> first, no prompt...
>
> Thanks,
> Richard
> KF5OIM
> _______________________________________________
> Trustedqsl-testing mailing list
> Tru...@li...
> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>
--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA
|
|
From: Richard S. <hob...@gm...> - 2023-09-18 02:10:11
|
On Sun, Sep 17, 2023 at 8:10 AM Rick Murphy <k1m...@gm...> wrote: > I'd have a look at your upload logs on Logbook - are you seeing previously > uploaded QSOs showing up? > I didn't see any duplicates or anything > Note that this practice - upload everything and let the software filter > the new ones - is strongly discouraged. > Hence my concern, it's always filtered the duplicates before now. > The upload data kept by TQSL is per-computer so QSOs uploaded from one > computer won't be recorded on any others (unless you backup the first and > restore the TBK to the others.) > I only keep a log on my desktop. If I do happen to work from my laptop I copy the ADIF files over. What platform are you using? > Fedora Linux 38. I've been the package maintainer for several years now. Thanks, Richard KF5OIM |
|
From: Rick M. <k1m...@gm...> - 2023-09-18 02:37:06
|
On Sun, Sep 17, 2023 at 10:14 PM Richard Shaw <hob...@gm...> wrote:
> On Sun, Sep 17, 2023 at 8:10 AM Rick Murphy <k1m...@gm...> wrote:
>
>> I'd have a look at your upload logs on Logbook - are you seeing
>> previously uploaded QSOs showing up?
>>
>
> I didn't see any duplicates or anything
>
Then nothing got re-uploaded. Seems strange. But - see below. There is
something wrong here.
> ...
>
>> What platform are you using?
>>
>
> Fedora Linux 38. I've been the package maintainer for several years now.
>
That makes it easy. I develop on Fedora and move to the other platforms.
Currently I'm running F38.
I just tried this and saw the same thing: signing a log with mostly
uploaded QSOs and they just went through.
I'll dig in as to why - this isn't intended.
73,
-Rick
--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA
|
|
From: Rick M. <k1m...@gm...> - 2023-09-18 11:33:12
Attachments:
dupefix.patch
|
The cause here is that the data being returned by the upload database query
is getting overwritten by sqlite so TQSL sees random garbage.
Fixed by making a copy of the data and managing release of that so it
sticks around until I need it.
Since you're building from source, patch attached. This will of course be
fixed in the release candidate,
Thanks for discovering this!
73,
-Rick
On Sun, Sep 17, 2023 at 10:36 PM Rick Murphy <k1m...@gm...> wrote:
> On Sun, Sep 17, 2023 at 10:14 PM Richard Shaw <hob...@gm...>
> wrote:
>
>> On Sun, Sep 17, 2023 at 8:10 AM Rick Murphy <k1m...@gm...>
>> wrote:
>>
>>> I'd have a look at your upload logs on Logbook - are you seeing
>>> previously uploaded QSOs showing up?
>>>
>>
>> I didn't see any duplicates or anything
>>
>
> Then nothing got re-uploaded. Seems strange. But - see below. There is
> something wrong here.
>
>
>> ...
>>
>>> What platform are you using?
>>>
>>
>> Fedora Linux 38. I've been the package maintainer for several years now.
>>
>
> That makes it easy. I develop on Fedora and move to the other platforms.
> Currently I'm running F38.
> I just tried this and saw the same thing: signing a log with mostly
> uploaded QSOs and they just went through.
> I'll dig in as to why - this isn't intended.
> 73,
> -Rick
> --
> Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA
>
--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA
|
|
From: Richard S. <hob...@gm...> - 2023-09-18 23:03:24
|
On Mon, Sep 18, 2023 at 6:33 AM Rick Murphy <k1m...@gm...> wrote: > The cause here is that the data being returned by the upload database > query is getting overwritten by sqlite so TQSL sees random garbage. > Fixed by making a copy of the data and managing release of that so it > sticks around until I need it. > Since you're building from source, patch attached. This will of course be > fixed in the release candidate, > > Thanks for discovering this! > I can confirm it works for me. Thanks! Richard KF5OIM |
Thanks for helping keep SourceForge clean.
X