|
|
Changing status. Seems to be more work left. |
|
|
Defect still exists in build 790.
Error.png (12,568 bytes) |
|
|
I think there are two causes to this issue. One is that the default database used the HRDCLI is configurable; and it's possible that users end up in a state where that configuration is invalid after they delete the default database. They're likely to do so because we instruct them to (see related bug). In that state, the user has no idea they're incorrectly configured because we don't give a warning when the configured database is deleted; and we don't give an error at startup when the invalid configuration is observable. Even if the database used for the network interfaces to the logbook is correctly configured, the insertion may fail for any number of reasons. There is no error handling in the HRDCLI code for the "add" verb. I've added some, so now we'll at least report an error if something goes wrong. I've never been able to reproduce this problem, so I'm unfortunately doing a bit of inductive reasoning. But I think addressing those issues will remedy this problem for our customers. |
|
|
I believe this issue is addressed with this checkin: https://hrdsoftware.visualstudio.com/HRD/_versionControl/changeset/4132 |
|
|
Unable to test this due to insufficient knowledge. |
|
|
I have personal experience of this defect, and I know of several QSO Relay users that have also experienced it. The workaround has been to have an Access database tab open simultaneously to the desired MySQL/MariaDB or SQL Server database. With 6.4.0.840 installed, I closed the Access database and ran my usual suite of Logbook API test case scripts and the defect became evident. Refer to the ‘Test Case Results with 6.4.0.840.pdf’ attachment in which test case 06 (pages 2 and 3) passed with Logbook reporting it ‘Added 44 Fields to ‘My Logbook - MySQL...’, but test case 07 (page 3) failed as the contact logged in test 06 could not be found, Similar results with test cases 08 and 09 on pages 3 and 4. I then installed 6.4.0.842 and reran the same suite of tests, and this time they all passed without having the Access database open – just my MySQL logbook database. In the past I have found that the I could still log contacts without the Access database being open on occasions, but it became my practice to keep it open to prevent it from reoccurring at an inopportune time. So, I will keep running the test case suite at various times over the next couple of days and report back. But at this stage it looks like it has been fixed. Good work Mike B! This defect has some visibility in the JTAlert JT65/FT8 mode community, and I am sure this will be seen as a significant gain. A big ‘thumbs up’ from me at least. 73 Chris VK2BYI. Test Case Results with 6.4.0.840.pdf (42,319 bytes) Test Case Results with 6.4.0.842.pdf (42,255 bytes) |
|
|
Closed the "placebo tab" and then added 7 QSOs via JT Alert 2.10.17. No failures noted. DB is an external Maria DB. The change seems successful but I will continue to monitor. |
- Anonymous
