eikek / eikek/sharry

The file is incomplete (105%). Try uploading again.

Open
#899 22 comments 0 reactions 0 assignees View on GitHub
Dominant language
Elm
Stars
1.3k
Forks
72
Avg merge
21h 30m
Merged PRs (30d)
1

Description

Hi community,

I am trying to setup sharry on my k3s cluster and it seems the work out fine except that for every upload there is an error about incomplete file upload (ranging from 103 - 105 %)
![image](https://user-images.githubusercontent.com/22686024/198876986-9cc57512-9d44-47e7-acbe-8de19d718336.png)

Some details on my setup :
- deployment is using the dockerhub eikek0/sharry latest image tag
- kubernetes node is arm64 based
- config: |
sharry.restserver {
base-url = "https://sharry.xxxmydomainxxx.be"
bind {
address = "0.0.0.0"
port = {{ .Values.service.main.ports.http.port }}
}
backend {
auth {
fixed {
enabled = true # set to true to enable this auth provider
user = "admin"
password = "admin"
order = 10
}
}
}
}

I set log-level to debug and could see the following errors :
2022.10.30 11:46:40:0000 [io-comp...] [WARN ] org.http4s.blazecore.util.IdentityWriter - Will not write more bytes than what was indicated by the Content-Length header (347753)
2022.10.30 11:46:40:0000 [io-comp...] [ERROR] org.http4s.blaze.server.Http1ServerStage$$anon$1 - Error writing body

Not sure if this is related.

I tried different versions, also changed to file store VS database, tried disabling the checksum but nothing seems to make a difference.
Any idea how to further troubleshoot would be appreciated.

Best regards,
Nico

Contributor guide

Open the contributing guide

Research direction

Start with the k3s deployment and the debug log showing the Content-Length warning from http4s. Reproduce an upload while checking the deployment and server behavior; the issue is done when uploads no longer report 103–105% completion and the cause and verification steps are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, kubernetes
Domain
backend, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.