eikek/sharry

Error message : 106% percent over 100

Opened this issue · 8 comments

bonnebulle commented

Hello
I just installed Sharry, Rasbian 32bit .deb file
Sharry 1.13.1 (#c06d164b)
I run in production (hostname URL)
All works well

But, every time, my uploads output an error message (under files)
"The file is incomplete (106%). Try uploading again."
"Le fichier est incomplet (106%). Essayer à nouveau."
Looks a little problem to fix

Do you need more information for debug ?
Thanks

Berehum commented

For me it was fixed by disabling the checksums, so it might have to do something with that.

bonnebulle commented 
compute-checksum = {
      # Setting this to false disables computation of checksums completely.
      enable = false
      . . .

Still have the same issue !
I will search for some other clues !
thanks

eikek commented

This is probably a duplicate of #899 ? I need to somehow debug this. I couldn't reproduce it when I was looking at it last time.

bonnebulle commented

yes it'is, thanks
I will share my futur tests
thanks for the advice

bonnebulle commented

By re-reading my issue here... I see I forgot to mention something important.

First, I have this error message on every upload (with different percentage)..

But, every time, the file ends well to upload... and I can display my file without problem.

It is why I said 'it should be a easy error to fix' (just not display error message if upload is over 100% !)

Thanks again I try many uploaders/sharing systems, this one looks more robust, with much more admin options !

Ravenbs commented

Fresh installation in Ubuntu. Same Error: Any Idea how to help debugging or fix this?
image
Disable the checksumm dont change anything.
I use default configuration with H2 but moved the file location for it to /home/sharry/...

And i Cant find a vew very important things in the docu:

  • how to quit / Restart the program instead of "killall java" and start again
Torstein-Eide commented

Can confirm, same issue.

Debian 12
installed from: sharry-restserver_1.14.0_all.deb

Looks like it tide to the database, if change the default option to filesystem it happy.

eikek commented

thanks for all the information! I should be able to reproduce it, it is most likely an issue with the H2 database option. only need to find the time to take a deeper look