OpenDIAS 0.9 beta feedback

[greg.su...@gmail.com]

Hi all,

Firstly, awesome work on openDIAS - been looking for something like this for a long time. Overall, it's very nice. However, all betas have rough edges, so here's my feedback so far. For the record, I've scanned about 25 docs so far, on an HP AIO C4500

* Issues detecting a scanner shared over the network via saned - Wayne and I are already discussing this off list, but I'm listing it here for the record.

* Login credentials don't prompt for browser storage - I tend to use random-generated passwords stored in Firefox/Chrome for most webservices here, but openDIAS doesn't seem to hook into that storage

* Popups appear in odd places - particularly when offering completions for tag names, the list of completions seems to appear in random places on the page. Screenshot available on request

* Unrelated error popups - I _think_ these are scanner-related, but as I'm not on the Acquire page when the pop up, I'm thinking they probably shouldn't be shown. I'll get a screenshot next time it happens - I can't reliably reproduce it, sadly.

* Inconsistent date formats - in a document it's YYYY/MM/DD but in the filter it's YYYY-MM-DD

* Bad dates in filter condition cause error popups on focus_change - these should probably only be shown when you click the filter button

* Occaisonal total crash of the openDIAS process on the server - happened twice now, I've upped the log verbosity to try and catch it next time. Both previous occurances were immediately after a scan.

Pretty much all cosmetic - is there a bug tracker to submit these (and any more I find) to?

Also, is there an RSS feed for new builds? I saw 0.9.3b is out, but if I hadn't come to the homepage I wouldn't have known....

Cheers,

Greg

[greg.su...@gmail.com]

On Tuesday, 16 April 2013 17:14:47 UTC+1, greg.su...@gmail.com wrote:

* Occaisonal total crash of the openDIAS process on the server - happened twice now, I've upped the log verbosity to try and catch it next time. Both previous occurances were immediately after a scan.

Further update on this - it's happening at a rate of once per 10 scans, and the error popup is:

 [a002] Error while talking to the server: error

There's nothing logged to the OpenDias logs, not even at log level 4. My only workaround is to keep a shell open on the openDias server to restart the process while scanning, but that means I can't leave my wife to do any scanning, as it's bound to choose that time to fall over. Pretty nasty.

Anything further I can do to debug?

Greg

 

[Wayne Booth]

Hi,

Thanks for the feedback. I've added each of these issues to the git issues tracker and marked them for fixing before the 0.9 version is finally released.

Wayne Booth

--
You received this message because you are subscribed to the Google Groups "openDIAS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opendias+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Wayne Booth]

Hi,
This is worrying. I've got a sneaky suspicion it git something to do with the calculation of the perceptual hash after a scan.
I've updated the git issue, and will give this some urgent attention.

Cheers

Wayne Booth

--

[greg.su...@gmail.com]

On Thursday, 18 April 2013 17:30:43 UTC+1, Wayne Booth wrote:

Hi,

Thanks for the feedback. I've added each of these issues to the git issues tracker and marked them for fixing before the 0.9 version is finally released

If thats the preferred venue I'll start reporting further bugs/suggestions there then :)