|
|
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 |
- Anonymous
